From: EBo <ebo@sandien.com>
To: <9fans@9fans.net>
Subject: Re: [9fans] 9vx patches [was: 9vx bootimage build instructions?]
Date: Thu, 26 May 2011 13:17:01 -0500 [thread overview]
Message-ID: <e98d91966a301078ccd42fea683ad682@swcp.com> (raw)
In-Reply-To: <bb704c6f4f90e1c11121cde9e665c471@ladd.quanstro.net>
On Thu, 26 May 2011 11:34:29 -0400, erik quanstrom wrote:
>> ... it to high gives me a warning that there are to many procs for
>> devproc...
>
> this is a bug in the warning message.
>
> ; diffy -c devproc.c
> ...
> + #define SLOTBITS 23 /* number of bits in the slot */
> + #define SLOTMASK ((1<<SLOTBITS)-1 << QSHIFT)
> ...
Thanks, I have added this patch to my ebuilds.
The system still crashes with very large numbers of procs (I think it
is overrunning the static definition of libvx32/proc.c vxproc
*procs[VXPROCSMAX]), but for now spawning 64 tasks is ok for
development, but all the tests are shooting for 512. It would be nice
to get all the systems running consistently. Any suggestions are
greatly appreciated.
EBo --
next prev parent reply other threads:[~2011-05-26 18:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 3:27 [9fans] 9vx bootimage build instructions? EBo
2011-05-26 3:37 ` erik quanstrom
2011-05-26 3:58 ` EBo
2011-05-26 4:05 ` EBo
2011-05-26 4:18 ` Devon H. O'Dell
2011-05-26 4:24 ` Bakul Shah
2011-05-26 7:40 ` yy
2011-05-26 14:06 ` [9fans] 9vx patches [was: 9vx bootimage build instructions?] EBo
2011-05-26 14:26 ` Devon H. O'Dell
2011-05-26 16:39 ` [9fans] hgfs? Bakul Shah
2011-05-26 22:12 ` simon softnet
2011-05-26 23:24 ` Iruatã Souza
2011-05-27 0:16 ` erik quanstrom
2011-05-27 8:12 ` Bakul Shah
2011-05-27 12:21 ` erik quanstrom
2011-05-27 14:45 ` Lucio De Re
2011-05-27 17:18 ` Bakul Shah
2011-05-27 17:30 ` erik quanstrom
2011-05-26 15:34 ` [9fans] 9vx patches [was: 9vx bootimage build instructions?] erik quanstrom
2011-05-26 18:17 ` EBo [this message]
2011-05-26 18:58 ` erik quanstrom
2011-05-26 19:17 ` EBo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e98d91966a301078ccd42fea683ad682@swcp.com \
--to=ebo@sandien.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).