From: Chris Wedgwood <cw@f00f.org>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: "Jeffrey E. Hundstad" <jeffrey.hundstad@mnsu.edu>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Steve Lord <lord@xfs.org>,
linux-xfs@oss.sgi.com, xfs-masters@oss.sgi.com, nathans@sgi.com,
Cahya Wirawan <cwirawan@email.archlab.tuwien.ac.at>,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL and XFS on 4KSTACKS=n
Date: Tue, 20 Jul 2004 13:42:38 -0700 [thread overview]
Message-ID: <20040720204238.GA3051@taniwha.stupidest.org> (raw)
In-Reply-To: <20040720195012.GN14733@fs.tum.de>
On Tue, Jul 20, 2004 at 09:50:12PM +0200, Adrian Bunk wrote:
> 1. let 4KSTACKS depend on EXPERIMENTAL
i don't like this change, despite what i might have claimed earlier :)
the reason i say this is if XFS blows up with 4K stacks then it
probably can with 8K stacks but it will be much harder, so it's not
really fixing anything but just papering over the problem
the reason for this is 8K stacks means you don't have separate irq
stacks, so if and interrupt comes along at the right time and the
codes paths are just right, you can still overflow (arguably you have
less overall space than with 4K stacks and separate irq stacks)
that said, separate irq stacks *and* 8k thread stacks would be safe,
but i'd love to see ideas on how to get the stack utilization down
(it's actually really hard)
--cw
next prev parent reply other threads:[~2004-07-20 20:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 11:44 4K stack kernel get Oops in Filesystem stress test Cahya Wirawan
2004-07-20 12:04 ` Steve Lord
2004-07-20 14:39 ` Jeffrey E. Hundstad
2004-07-20 19:50 ` [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL and XFS on 4KSTACKS=n Adrian Bunk
2004-07-20 20:42 ` Chris Wedgwood [this message]
2004-07-20 20:50 ` Adrian Bunk
2004-07-20 20:58 ` Chris Wedgwood
2004-07-29 6:09 ` Nathan Scott
2004-07-29 11:42 ` Adrian Bunk
2004-07-29 11:46 ` Arjan van de Ven
2004-07-29 21:11 ` Adrian Bunk
2004-07-29 21:44 ` Chris Wedgwood
2004-07-29 22:30 ` [xfs-masters] " Nathan Scott
2004-08-01 19:02 ` [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL Adrian Bunk
2004-07-29 15:42 ` [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL and XFS on 4KSTACKS=n Mika Bostrom
2004-07-29 16:09 ` Zwane Mwaikambo
2004-07-29 16:36 ` [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL and XFS on 4KSTACKS Mika Bostrom
2004-07-22 7:27 ` 4K stack kernel get Oops in Filesystem stress test Amon Ott
2004-07-29 2:14 ` Nathan Scott
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=20040720204238.GA3051@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=akpm@osdl.org \
--cc=bunk@fs.tum.de \
--cc=cwirawan@email.archlab.tuwien.ac.at \
--cc=jeffrey.hundstad@mnsu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=lord@xfs.org \
--cc=nathans@sgi.com \
--cc=torvalds@osdl.org \
--cc=xfs-masters@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.