9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Maximal number of processes
Date: Thu,  9 Jan 2014 20:45:40 +1100	[thread overview]
Message-ID: <CAJQxxw=u0qpRyRLwht1NE=xtzJZrVUdEKifSQoH3qnpunW3R2w@mail.gmail.com> (raw)
In-Reply-To: <CAGNd-2N++nfx65sNWaRr9UfVoSrWLiU4=YTt_Ly3_0+pwJh-1w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]

suck it and see, the answerers didn't understand the question. add
nproc=XXX to plan9.ini and use the environment, or hard code code it. i'd
like to see your results for nproc=50 and nproc=5000.

brucee


On 9 January 2014 19:08, Pavel Klinkovský <pavel.klinkovsky@gmail.com>wrote:

> Hi Steven,
>
>
>     conf.nproc = 100 + ((conf.npage*BY2PG)/MB)*5;
>>     if(cpuserver)
>>             conf.nproc *= 3;
>>     if(conf.nproc > 2000)
>>             conf.nproc = 2000;
>>
>> In general, you will find that 2000 is the highest allowable due to
>> limits imposed by proc.c.
>
>
> but if I understand it correctly it is just "soft limit", not a "hard" one
> inborn in CPU architecture.
>
> By the hard limit I consider something like "maximal capacity of GDT, LDT"
> or something similar, if exists.
>
>
>> At the end of the day, the only way to be sure is to read the source.
>>
>
> I did (of course, I am not an expert on Plan9 kernel), and I did not find
> any "hard limit" there.
> However to be sure I issued my question here.
>
> Pavel
>

[-- Attachment #2: Type: text/html, Size: 1976 bytes --]

  reply	other threads:[~2014-01-09  9:45 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
2014-01-09  8:08   ` Pavel Klinkovský
2014-01-09  9:45     ` Bruce Ellis [this message]
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='CAJQxxw=u0qpRyRLwht1NE=xtzJZrVUdEKifSQoH3qnpunW3R2w@mail.gmail.com' \
    --to=bruce.ellis@gmail.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).