From: "H. Peter Anvin" <hpa@kernel.org>
To: Denys Vlasenko <vda.linux@googlemail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: do not grow initial process stack so much
Date: Thu, 17 Jul 2008 16:12:25 -0700 [thread overview]
Message-ID: <487FD1D9.9020100@kernel.org> (raw)
In-Reply-To: <200807162332.37741.vda.linux@googlemail.com>
Denys Vlasenko wrote:
>
> I do not see, though, why this can be useful for x86. The pages
> are not mapped anyway, so accessing them still causes page faults.
> No speedup for, say, rapidly spawning processes which need ~60k
> of stack right away. They will still fault in kernel, right?
>
They will fault in the kernel, but only to fill the page tables, so it
would cut down on latency.
I do *NOT* believe we should make this an x86-only change. If it should
be architecture-dependent I'd rather find the architectures that do need it.
However, before changing this I really want to see some of the history
about why it's that way in the first place.
-hpa
prev parent reply other threads:[~2008-07-17 23:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 21:32 [PATCH] x86: do not grow initial process stack so much Denys Vlasenko
2008-07-17 23:12 ` H. Peter Anvin [this message]
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=487FD1D9.9020100@kernel.org \
--to=hpa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vda.linux@googlemail.com \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox