[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] [PATCH v6 0/4] ext4: Coordinate data-only flush requests sent by fsync
- From: Christoph Hellwig <hch lst de>
- To: Neil Brown <neilb suse de>
- Cc: Jens Axboe <axboe kernel dk>, Jan Kara <jack suse cz>, Mike Snitzer <snitzer redhat com>, linux-kernel <linux-kernel vger kernel org>, linux-raid vger kernel org, Tejun Heo <tj kernel org>, dm-devel redhat com, Andreas Dilger <adilger kernel dilger ca>, Josef Bacik <josef redhat com>, Mingming Cao <cmm us ibm com>, Keith Mannthey <kmannth us ibm com>, Theodore Ts'o <tytso mit edu>, linux-ext4 vger kernel org, Ric Wheeler <rwheeler redhat com>, Christoph Hellwig <hch lst de>, Alasdair G Kergon <agk redhat com>
- Subject: Re: [dm-devel] [PATCH v6 0/4] ext4: Coordinate data-only flush requests sent by fsync
- Date: Tue, 30 Nov 2010 17:43:01 +0100
On Tue, Nov 30, 2010 at 11:39:06AM +1100, Neil Brown wrote:
> Would it not be sufficient to simply gather flushes while a flush is pending.
> i.e
> - if no flush is pending, set the 'flush pending' flag, submit a flush,
> then clear the flag.
> - if a flush is pending, then wait for it to complete, and then submit a
> single flush on behalf of all pending flushes.
>
> That way when flush is fast, you do a flush every time, and when it is slow
> you gather multiple flushes together.
We can even optimize the second flush away if no other I/O has
completed since the first flush has started. That will always be the
case for SATA devices as the cache flush command is not queued.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]