9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 9vx patches [was: 9vx bootimage build instructions?]
Date: Thu, 26 May 2011 14:58:11 -0400	[thread overview]
Message-ID: <242134316844bdf04a63ebc86cbd5cab@ladd.quanstro.net> (raw)
In-Reply-To: <e98d91966a301078ccd42fea683ad682@swcp.com>

>  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.

unless someone has broken 9vx since i last pulled, the code has
that case handled.

	for (pno = 0; ; pno++) {
		if (pno == VXPROCSMAX) {
			errno = EAGAIN;
			return NULL;
		}
		if (procs[pno] == 0)
			break;
	}

if you follow vxproc_alloc calls, you'll see that each
caller checks the return value and does something reasonable.

given this,

main.c:318: 	conf.nproc = 100 + ((conf.npage*BY2PG)/MB)*5;
main.c:319: 	if(conf.nproc > 2000)
main.c:320: 		conf.nproc = 2000;

i'd suspect that the real problem is you're not giving 9vx enough
kernel memory.  try setting kernelpercent to something largeish.

but of course, i'm just guessing.  it would be helpful to have some
debugging output.

- erik



  reply	other threads:[~2011-05-26 18:58 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
2011-05-26 18:58           ` erik quanstrom [this message]
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=242134316844bdf04a63ebc86cbd5cab@ladd.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).