From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: a modest proposal for 4kstacks & xfs
Date: Tue, 13 Feb 2007 10:05:48 -0800 [thread overview]
Message-ID: <45D1FDFC.20407@sandeen.net> (raw)
XFS continues to come up against 4k stacks, despite the best efforts of
several people to slim down xfs a bit (and in fact it seems ok over
simple storage these days), people are always able to stack up enough IO
path to push the limits of a 4k stack.
What would people think of adding a module parameter to xfs, i.e.
modprobe xfs 4kstacks_may_break=1
or somesuch; and without this modprobe would fail on a 4kstacks kernel
with a "helpful" message. This would at least require some positive
action on the admin's part to acknowledge that there is some risk to
using xfs with 4k stacks. (unfortunately something like the Fedora
installer would of course have to add this by default when installing on
xfs, maybe it could also warn the user of the risk...)
I hate to further the meme of "xfs won't work with 4kstacks" but the
truth is that there are IO path scenarios where it can lead to problems.
What do folks think; useful? pointless? too heavy-handed?
-Eric
next reply other threads:[~2007-02-13 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 18:05 Eric Sandeen [this message]
2007-02-13 20:13 ` a modest proposal for 4kstacks & xfs Chris Wedgwood
2007-02-14 20:48 ` David Chinner
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=45D1FDFC.20407@sandeen.net \
--to=sandeen@sandeen.net \
--cc=xfs@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