| To: | Chris Mason <chris.mason@xxxxxxxxxx> |
|---|---|
| Subject: | Re: buffered writeback torture program |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Thu, 21 Apr 2011 13:41:21 -0400 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, linux-fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>, linux-ext4 <linux-ext4@xxxxxxxxxxxxxxx>, xfs <xfs@xxxxxxxxxxx>, jack <jack@xxxxxxx>, axboe <axboe@xxxxxxxxx>, dchinner <dchinner@xxxxxxxxxx> |
| In-reply-to: | <1303407205-sup-6141@think> |
| References: | <1303322378-sup-1722@think> <20110421083258.GA26784@xxxxxxxxxxxxx> <1303407205-sup-6141@think> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
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. |
| Previous by Date: | Re: buffered writeback torture program, Chris Mason |
|---|---|
| Next by Date: | Re: buffered writeback torture program, Andreas Dilger |
| Previous by Thread: | Re: buffered writeback torture program, Chris Mason |
| Next by Thread: | Re: buffered writeback torture program, Andreas Dilger |
| Indexes: | [Date] [Thread] [Top] [All Lists] |