From: Rik van Riel <riel@conectiva.com.br>
To: Dave McCracken <dmccr@us.ibm.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Issue with max_threads (and other resources) and highmem
Date: Tue, 23 Oct 2001 19:59:08 -0200 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.33L.0110231911210.3690-100000@imladris.surriel.com> (raw)
In-Reply-To: <91510000.1003871155@baldur>
On Tue, 23 Oct 2001, Dave McCracken wrote:
> --On Tuesday, October 23, 2001 18:52:35 -0200 Rik van Riel
> <riel@conectiva.com.br> wrote:
>
> > I submitted a patch a while ago to set the number way lower,
> > which was accepted by Alan and in the -ac kernels. A few months
> > later Linus followed and changed the limit in his kernels, too.
>
> Ok, that's what I get for reading the comment and not deciphering the
> code...
*sigh* So my updated comment got backed out again ;/
Linus, what do you have against correct documentation ? ;)
> But there's still a problem. The value for mempages is all of physical
> memory including highmem, so a machine with a sufficient amount of high
> memory can set max_threads to a value way too high, given that most if not
> all of the resources it's trying to limit have to come from normal memory
> and not high memory.
Indeed, this needs to be fixed. A sane upper limit for
max_threads would be 10000, this also keeps in mind the
fact that we only have 32000 possible PIDs, some of which
could be taken by task groups, etc...
regards,
Rik
--
DMCA, SSSCA, W3C? Who cares? http://thefreeworld.net/ (volunteers needed)
http://www.surriel.com/ http://distro.conectiva.com/
next prev parent reply other threads:[~2001-10-23 21:59 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
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 [this message]
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=Pine.LNX.4.33L.0110231911210.3690-100000@imladris.surriel.com \
--to=riel@conectiva.com.br \
--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 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).