From: Dave McCracken <dmccr@us.ibm.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Issue with max_threads (and other resources) and highmem
Date: Tue, 23 Oct 2001 16:05:55 -0500 [thread overview]
Message-ID: <91510000.1003871155@baldur> (raw)
In-Reply-To: <Pine.LNX.4.33L.0110231850100.3690-100000@imladris.surriel.com>
In-Reply-To: <Pine.LNX.4.33L.0110231850100.3690-100000@imladris.surriel.com>
--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... The actual calculation is mempages / (THREAD_SIZE/PAGE_SIZE) / 8
where THREAD_SIZE is 2 pages on i386. If I read it right this means it's
limiting it to 1/8 physical memory instead of half.
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.
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 21:07 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 [this message]
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=91510000.1003871155@baldur \
--to=dmccr@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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