From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Maximal number of processes
Date: Fri, 10 Jan 2014 09:11:04 +0000 [thread overview]
Message-ID: <CAOw7k5iioR9WVVGg5fejTYoH98cpegE4NHcY8yWH1w3aqKuZrg@mail.gmail.com> (raw)
In-Reply-To: <CAGNd-2N++nfx65sNWaRr9UfVoSrWLiU4=YTt_Ly3_0+pwJh-1w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
On 9 January 2014 08:08, Pavel Klinkovský <pavel.klinkovsky@gmail.com>wrote:
> By the hard limit I consider something like "maximal capacity of GDT, LDT"
> or something similar, if exists.
GDT and even Tss are per-processor; ldt isn't used.
As to soft limits, apart from the few linear searches mentioned, which
could be eliminated if necessary,
for instance by tracking process groups, the main constraint is the kernel
virtual address space and physical memory consumed by
the KSTACK for each process. It's only 4k (in 32 bit mode) but it might be
difficult to handle hundreds of thousands of the things
comfortably.
I tried 3000, on a lowly Atom with 2 Gb RAM:
nova% ps|wc -l
2992
and it seemed fine. Do I hear "more!"?
nova% ps|wc -l
3991
nova% cat /dev/swap
2135371776 memory
4096 pagesize
48986 kernel
28594/472345 user
0/320000 swap
35004768/142308320 kernel malloc
0/16777216 kernel draw
At that point I decided to quite while I was still ahead. I'd probably need
a bit more DRAM to do anything much with all of them
(they were only running sleep 60), but that's easy to find. Except that
they'll have changed DRAM types again no doubt.
[-- Attachment #2: Type: text/html, Size: 2147 bytes --]
next prev parent reply other threads:[~2014-01-10 9:11 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
2014-01-09 16:36 ` Pavel Klinkovský
2014-01-10 9:11 ` Charles Forsyth [this message]
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=CAOw7k5iioR9WVVGg5fejTYoH98cpegE4NHcY8yWH1w3aqKuZrg@mail.gmail.com \
--to=charles.forsyth@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).