From: Arjan van de Ven <arjan@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andi Kleen <andi@firstfloor.org>,
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 06:54:51 -0700 [thread overview]
Message-ID: <20080416065451.78329e12@laptopd505.fenrus.org> (raw)
In-Reply-To: <20080416124728.GA5050@elte.hu>
On Wed, 16 Apr 2008 14:47:28 +0200
Ingo Molnar <mingo@elte.hu> wrote:
>
> * 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
well that and the fact that RH had customers who had major issues at fewer threads
with 8Kb versus fragmentation.
on 32 bit with a bunch of ram, there's just not enough lowmem around to not have it
fragmented to hell and back.
x86_64 is better off there, it doesn't really have lowmem, and also buddy works better
against fragmentation the bigger the zone it works with it seems
(or at least, the lower the ratio of long term pinned pages is)
--
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-04-16 13:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 13:47 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
2008-04-16 13:54 ` Arjan van de Ven [this message]
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=20080416065451.78329e12@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=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
all inboxes | Powered by JetHome®