9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Maximal number of processes
Date: Wed,  8 Jan 2014 11:55:26 -0500	[thread overview]
Message-ID: <421bd46d53070799c40d875abe2af588@coraid.com> (raw)
In-Reply-To: <CAGGHmKHP17NsSApo=d8TZRC1b8iLRo7LsJ3_efHFzaDu-4Wk2w@mail.gmail.com>

> In general, you will find that 2000 is the highest allowable due to
> limits imposed by proc.c. Other architectures can (and will) place
> additional restrictions. A non-FCSE ARM implementation could elect to
> only support 256 processes to avoid additional switching overhead for
> example.

i had a different interpretation of the op's definition of "hard",
since memory limits were deemed irrelevant.

what limits are you thinking of in proc.c?

the only hard limit in the portable code that i see is in devproc.c,
the number of processes needs to fit in the space reserved in
the qid.  i'd forgotten about that since its 2^23, which is so
large that it might safely be forgotten.

there are plenty of soft limits in the portable code.  linear scans
of the process table are made in a number of places, for example.
and of course process allocation must be static due to the locking
schemes used.  (cf. the recent procalarm discussion.)

- erik



  reply	other threads:[~2014-01-08 16:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08  8:28 Pavel Klinkovský
2014-01-08 10:15 ` erik quanstrom
2014-01-08 15:23 ` Steven Stallion
2014-01-08 16:55   ` erik quanstrom [this message]
2014-01-09  8:08   ` Pavel Klinkovský
2014-01-09  9:45     ` Bruce Ellis
2014-01-09 16:36       ` Pavel Klinkovský
2014-01-10  9:11     ` Charles Forsyth
2014-01-10  9:15       ` Charles Forsyth
2014-01-10  9:38         ` Bruce Ellis
2014-01-10 13:48         ` erik quanstrom
2014-01-10 14:00           ` erik quanstrom
2014-01-10 14:24             ` Pavel Klinkovský

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=421bd46d53070799c40d875abe2af588@coraid.com \
    --to=quanstro@labs.coraid.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).