From: Andi Kleen <ak@muc.de>
To: Dave McCracken <dmccr@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Issue with max_threads (and other resources) and highmem
Date: 23 Oct 2001 22:36:51 +0200 [thread overview]
Message-ID: <k28ze2drfg.fsf@zero.aec.at> (raw)
In-Reply-To: <72940000.1003868385@baldur>
In-Reply-To: Dave McCracken's message of "Tue, 23 Oct 2001 15:19:45 -0500"
In article <72940000.1003868385@baldur>,
Dave McCracken <dmccr@us.ibm.com> writes:
> What's the best approach here?
I would just limit it to a reasonable max value; e.g. 10000
if someone needs more than 10000 threads/processes he/she can set sysctls
manually. The current scheduler would choke anyways if only a small
fraction of 10000 threads are runnable.
-Andi
next prev parent reply other threads:[~2001-10-23 20:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-23 20:19 Issue with max_threads (and other resources) and highmem Dave McCracken
2001-10-23 20:36 ` Andi Kleen [this message]
2001-10-23 20:46 ` Dave McCracken
2001-10-23 20:52 ` Rik van Riel
2001-10-23 21:05 ` Dave McCracken
2001-10-23 21:59 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2001-10-23 23:30 Dan Kegel
2001-10-23 23:35 ` Rik van Riel
2001-10-24 0:00 ` Dan Kegel
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=k28ze2drfg.fsf@zero.aec.at \
--to=ak@muc.de \
--cc=dmccr@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.