From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: david@lang.hm, Linux Kernel <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com, Christoph Hellwig <hch@infradead.org>,
Justin Piszcz <jpiszcz@lucidpixels.com>,
Alex Elder <aelder@sgi.com>, Mark Lord <kernel@teksavvy.com>,
Stan Hoeppner <stan@hardwarefreak.com>
Subject: Re: xfs: very slow after mount, very slow at umount
Date: Mon, 31 Jan 2011 14:17:20 -0500 [thread overview]
Message-ID: <20110131191720.GA2327@infradead.org> (raw)
In-Reply-To: <20110129073554.GC21311@dastard>
On Sat, Jan 29, 2011 at 06:35:54PM +1100, Dave Chinner wrote:
> Just because we can't do it right now doesn't mean it is not
> possible. Array/raid controller vendors need to implement the SCSI
> block limit VPD page, and if they do then stripe unit/stripe width
> may be exposed for the device in sysfs. However, I haven't seen any
> devices except for md and dm that actually export values that
> reflect sunit/swidth in the files:
I have access to a few big vendor arrays that export it, but I think
they are still running beta firmware versions.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-01-31 19:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D40C8D1.8090202@teksavvy.com>
2011-01-27 3:30 ` xfs: very slow after mount, very slow at umount Dave Chinner
2011-01-27 3:49 ` Mark Lord
2011-01-27 5:17 ` Stan Hoeppner
2011-01-27 15:12 ` Mark Lord
2011-01-27 15:40 ` Justin Piszcz
2011-01-27 16:03 ` Mark Lord
2011-01-27 19:40 ` Stan Hoeppner
2011-01-27 20:11 ` david
2011-01-27 23:53 ` Stan Hoeppner
2011-01-28 2:09 ` david
2011-01-28 13:56 ` Dave Chinner
2011-01-28 19:26 ` david
2011-01-29 5:40 ` Dave Chinner
2011-01-29 6:08 ` david
2011-01-29 7:35 ` Dave Chinner
2011-01-31 19:17 ` Christoph Hellwig [this message]
2011-01-27 21:56 ` Mark Lord
2011-01-28 0:17 ` Dave Chinner
2011-01-28 1:22 ` Mark Lord
2011-01-28 1:36 ` Mark Lord
2011-01-28 4:14 ` David Rees
2011-01-28 14:22 ` Mark Lord
2011-01-28 7:31 ` Dave Chinner
2011-01-28 14:33 ` Mark Lord
2011-01-28 23:58 ` Dave Chinner
2011-01-28 19:18 ` Martin Steigerwald
2011-01-27 20:24 ` John Stoffel
2011-01-27 23:41 ` Dave Chinner
2011-01-28 0:59 ` Mark Lord
2011-01-27 23:39 ` Dave Chinner
[not found] ` <4D40CDCF.4010301@teksavvy.com>
2011-01-27 3:43 ` Dave Chinner
2011-01-27 3:53 ` Mark Lord
2011-01-27 4:54 ` Mark Lord
2011-01-27 23:34 ` Dave 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=20110131191720.GA2327@infradead.org \
--to=hch@infradead.org \
--cc=aelder@sgi.com \
--cc=david@fromorbit.com \
--cc=david@lang.hm \
--cc=jpiszcz@lucidpixels.com \
--cc=kernel@teksavvy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stan@hardwarefreak.com \
--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