From: Dave McCracken <dmccr@us.ibm.com>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Issue with max_threads (and other resources) and highmem
Date: Tue, 23 Oct 2001 15:46:19 -0500 [thread overview]
Message-ID: <85870000.1003869979@baldur> (raw)
In-Reply-To: <k28ze2drfg.fsf@zero.aec.at>
In-Reply-To: <72940000.1003868385@baldur> <k28ze2drfg.fsf@zero.aec.at>
--On Tuesday, October 23, 2001 22:36:51 +0200 Andi Kleen <ak@muc.de> wrote:
> 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.
Yes, that would solve the max_threads problem. It should be fairly simple
to pick a reasonable number.
But my question is also about the other subsystems called from
start_kernel() that take memory size as an argument. This includes
vfs_caches_init() which in turn calls dcache_init(), and buffer_init() and
page_cache_init(). I haven't dug down to the bottom of all these
functions, but I'm guessing they really want to base their calculations on
available normal memory and not high memory.
Dave McCracken
======================================================================
Dave McCracken IBM Linux Base Kernel Team 1-512-838-3059
dmccr@us.ibm.com T/L 678-3059
next prev parent reply other threads:[~2001-10-23 20:47 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 [this message]
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=85870000.1003869979@baldur \
--to=dmccr@us.ibm.com \
--cc=ak@muc.de \
--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.