From: Nathan Scott <nathans@sgi.com>
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,
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: Thu, 29 Jul 2004 16:09:00 +1000 [thread overview]
Message-ID: <20040729060900.GA1946@frodo> (raw)
In-Reply-To: <20040720195012.GN14733@fs.tum.de>
On Tue, Jul 20, 2004 at 09:50:12PM +0200, Adrian Bunk wrote:
>
> The patch below does:
>
> 1. let 4KSTACKS depend on EXPERIMENTAL
> Rationale:
> 4Kb stacks on i386 are the future. But currently this option might still
> cause problems in some areas of the kernel. OTOH, 4Kb stacks isn't a big
> gain for most people.
> 2.6 is a stable kernel series, and 4KSTACKS=n is the safe choice.
> Once all issues with 4KSTACKS=y are resolved this can be reverted.
Seems fine.
> 2. let XFS depend on (4KSTACKS=n || BROKEN)
> Rationale:
> Mark Loy said:
> Don't use 4K stacks and XFS.
Who is Mark Loy? (and what does he know about XFS?)
> Mark this combination as BROKEN until XFS is fixed.
This part is not useful. We want to hear about problems
that people hit with 4K stacks so we can try to address
them, and it mostly works as is.
cheers.
--
Nathan
next prev parent reply other threads:[~2004-07-29 5:13 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
2004-07-20 20:50 ` Adrian Bunk
2004-07-20 20:58 ` Chris Wedgwood
2004-07-29 6:09 ` Nathan Scott [this message]
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=20040729060900.GA1946@frodo \
--to=nathans@sgi.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).