From: Christoph Hellwig <hch@infradead.org>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Christoph Hellwig <hch@infradead.org>,
Chris Mason <chris.mason@oracle.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>, xfs <xfs@oss.sgi.com>,
jack <jack@suse.cz>, axboe <axboe@kernel.dk>,
dchinner <dchinner@redhat.com>
Subject: Re: buffered writeback torture program
Date: Thu, 21 Apr 2011 14:02:13 -0400 [thread overview]
Message-ID: <20110421180213.GA19255@infradead.org> (raw)
In-Reply-To: <93CB867E-B908-4B38-A146-A9DC958ACF64@dilger.ca>
On Thu, Apr 21, 2011 at 11:59:37AM -0600, Andreas Dilger wrote:
> But doesn't XFS have potentially very large extents, especially in the case of files that were fallocate()'d or linearly written? If there is a single 8GB extent, and then random writes within that extent (seems very database like) grouping the all of the writes in the extent doesn't seem so great.
It doesn't cluster any writes in an extent. It only writes out
additional dirty pages directly following that one we were asked to
write out. As soon as we hit a non-dirty page we give up.
next prev parent reply other threads:[~2011-04-21 18:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 18:23 buffered writeback torture program Chris Mason
2011-04-20 22:06 ` Vivek Goyal
2011-04-21 11:09 ` Chris Mason
2011-04-21 15:25 ` Chris Mason
2011-04-21 15:35 ` Vivek Goyal
2011-04-21 16:55 ` Jan Kara
2011-04-21 16:57 ` Chris Mason
2011-04-21 20:44 ` Jan Kara
2011-04-21 8:32 ` Christoph Hellwig
2011-04-21 17:34 ` Chris Mason
2011-04-21 17:41 ` Christoph Hellwig
2011-04-21 17:59 ` Andreas Dilger
2011-04-21 18:02 ` Christoph Hellwig [this message]
2011-04-21 18:02 ` Chris Mason
2011-04-21 18:08 ` Christoph Hellwig
2011-04-21 18:29 ` Chris Mason
2011-04-21 18:43 ` Andreas Dilger
2011-04-21 18:47 ` Chris Mason
2011-04-21 18:00 ` Chris Mason
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=20110421180213.GA19255@infradead.org \
--to=hch@infradead.org \
--cc=adilger@dilger.ca \
--cc=axboe@kernel.dk \
--cc=chris.mason@oracle.com \
--cc=dchinner@redhat.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).