From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Thomas King <kingttx@tomslinux.homelinux.org>, xfs@oss.sgi.com
Subject: Re: Questions for article
Date: Wed, 4 Jun 2008 01:28:59 -0400 [thread overview]
Message-ID: <20080604052859.GA6509@infradead.org> (raw)
In-Reply-To: <4845C254.6050104@sandeen.net>
On Tue, Jun 03, 2008 at 05:14:44PM -0500, Eric Sandeen wrote:
> It's also not clear to me that this is really a critical feature for
> large filesystems; space allocation is not done block by block per se in
> xfs, as Mr. Newman seems (?) to imply (?) The block granularity is
> there throughout the fs but I'm not sure how much it matters in
> practice. Dave...?
For streaming I/O workloads it doesn't matter anymore, see Dave's 2006
OLS talk. The direct to bio I/O path mitigates any blocksize impact.
next prev parent reply other threads:[~2008-06-04 5:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 20:48 Questions for article Thomas King
2008-06-03 22:00 ` Martin K. Petersen
2008-06-03 22:14 ` Eric Sandeen
2008-06-03 22:19 ` Thomas King
2008-06-04 5:28 ` Christoph Hellwig [this message]
2008-06-04 5:31 ` Christoph Hellwig
2008-06-04 14:16 ` Thomas King
2008-06-04 15:06 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2008-06-03 15:34 Thomas King
2008-06-03 19:42 ` Justin Piszcz
2008-06-04 14:52 ` Emmanuel Florac
2008-06-02 21:50 Thomas King
2008-06-02 22:30 ` Eric Sandeen
2008-06-02 22:59 ` Andreas Dilger
2008-06-03 0:40 ` Eric Sandeen
2008-06-03 15:17 ` Thomas King
2008-06-03 15:10 ` Thomas King
2008-06-03 15:49 ` Martin K. Petersen
2008-06-03 22:07 ` Andreas Dilger
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=20080604052859.GA6509@infradead.org \
--to=hch@infradead.org \
--cc=kingttx@tomslinux.homelinux.org \
--cc=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 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.