From: Christoph Hellwig <hch@infradead.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
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 13:41:21 -0400 [thread overview]
Message-ID: <20110421174120.GA7267@infradead.org> (raw)
In-Reply-To: <1303407205-sup-6141@think>
On Thu, Apr 21, 2011 at 01:34:44PM -0400, Chris Mason wrote:
> Sorry, this doesn't do it. I think that given what a strange special
> case this is, we're best off waiting for the IO-less throttling, and
> maybe changing the code in xfs/ext4 to be a little more seek aware. Or
> maybe not, it has to get written eventually either way.
I'm not sure what you mean with seek aware. XFS only clusters
additional pages that are in the same extent, and in fact only does
so for asynchrononous writeback. Not sure how this should be more
seek aware.
next prev parent reply other threads:[~2011-04-21 17:41 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 [this message]
2011-04-21 17:59 ` Andreas Dilger
2011-04-21 18:02 ` Christoph Hellwig
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=20110421174120.GA7267@infradead.org \
--to=hch@infradead.org \
--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).