From: Andi Kleen <andi@firstfloor.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Denys Vlasenko <vda.linux@googlemail.com>, linux-kernel@vger.kernel.org
Subject: Re: Does process need to have a kernel-side stack all the time?
Date: Wed, 16 Apr 2008 15:02:08 +0200 [thread overview]
Message-ID: <4805F8D0.7000203@firstfloor.org> (raw)
In-Reply-To: <20080416124728.GA5050@elte.hu>
> no, the primary motivation Arjan and me started working on 4K stacks and
> implemented it was what Denys mentioned: i had a testcase that ran
> 50,000 threads before it ran out of memory - i wanted it to run 100,000
> threads. The improved order-0 behavior was just icing on the cake.
I checked the original changelog and it mentions both with the
dumb reason covered in one sentence and the stall issue deserving
a full paragraph.
Well frankly that was a dumb reason then. Ok I hadn't imagined you
both really spent time on something dumb :) The stall reason
at least made some sense, although I suspect it is obsolete by now.
My objection to the 100k threads would be less that they
shouldn't be needed (we all know that user space does dumb things), but
that when you have them either with 4k stacks (or 50k threads with 8k
stack) you're dangerously near lowmem exhaustion on 32bit and then
sooner or later the system will have trouble anyways from low lowmem.
It's fundamentally not a reliable setup.
-Andi
next prev parent reply other threads:[~2008-04-16 13:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 13:47 Does process need to have a kernel-side stack all the time? Denys Vlasenko
2008-04-14 14:17 ` Denis V. Lunev
2008-04-14 14:54 ` Denys Vlasenko
2008-04-14 15:21 ` Ingo Molnar
2008-04-14 17:44 ` Andi Kleen
2008-04-14 18:42 ` Denys Vlasenko
2008-04-16 12:47 ` Ingo Molnar
2008-04-16 13:02 ` Andi Kleen [this message]
2008-04-16 13:54 ` Arjan van de Ven
2008-04-16 13:59 ` Andi Kleen
2008-04-16 14:31 ` Arjan van de Ven
2008-04-16 14:20 ` Denys Vlasenko
2008-04-16 14:34 ` Arjan van de Ven
2008-04-14 23:21 ` Chris Snook
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=4805F8D0.7000203@firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vda.linux@googlemail.com \
/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