From: Dave Jones <davej@redhat.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL (fwd)
Date: Tue, 3 Aug 2004 14:26:19 +0100 [thread overview]
Message-ID: <20040803132619.GC12571@redhat.com> (raw)
In-Reply-To: <20040803131339.GB2746@fs.tum.de>
On Tue, Aug 03, 2004 at 03:13:39PM +0200, Adrian Bunk wrote:
> > So put && !4KSTACKS in the XFS configuration ?
> I originally did this additionally (including moving 4KSTACKS
> above XFS).
>
> But independent of the XFS problem, 4kb stacks currently risk additional
> breakage without real benefits for most users.
Just before the Fedora kernel got 4K stacks (which was before mainline),
in stress testing, I was hitting memory allocation bugs far sooner than
I was hitting stack overflows, so I don't think this claim has any bearing on reality.
It was far more commonplace for the kernel to struggle to find a free pair
of contiguous pages under extreme load. And as already mentioned,
those overflows _can_ be hit with an 8KB stack too, you just have to
try harder.
The 'real benefits' you aren't seeing are lots of failing order-1 allocations
under moderate to heavy load. You don't even need big iron boxes to see this,
(in fact, its easier to hit this problem on smaller underpowered boxes).
Dave
next prev parent reply other threads:[~2004-08-03 13:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 22:59 [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL (fwd) Adrian Bunk
2004-08-02 23:28 ` Andrew Morton
2004-08-03 0:45 ` Adrian Bunk
2004-08-02 23:56 ` Alan Cox
2004-08-03 13:13 ` Adrian Bunk
2004-08-03 13:26 ` Dave Jones [this message]
2004-08-03 20:11 ` Adrian Bunk
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=20040803132619.GC12571@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.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