From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <andi@firstfloor.org>
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 14:47:28 +0200 [thread overview]
Message-ID: <20080416124728.GA5050@elte.hu> (raw)
In-Reply-To: <87hce4uya8.fsf@basil.nowhere.org>
* Andi Kleen <andi@firstfloor.org> wrote:
> Denys Vlasenko <vda.linux@googlemail.com> writes:
>
> > A lot of effort went into minimizing of stack usage.
> > If I understand it correctly, one of the reasons for this
> > was to be efficient and not have lots of pages
> > used for stacks when we have a lot of threads
> > (tens of thousands).
>
> Actually the real reason the 4K stacks were introduced IIRC was that
> the VM is not very good at allocation of order > 0 pages and that only
> using order 0 and not order 1 in normal operation prevented some
> stalls.
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.
Ingo
next prev parent reply other threads:[~2008-04-16 12:47 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 [this message]
2008-04-16 13:02 ` Andi Kleen
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=20080416124728.GA5050@elte.hu \
--to=mingo@elte.hu \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--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