[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] [PATCH 2/5] dm: implement REQ_FLUSH/FUA support for bio-based dm
- From: Tejun Heo <tj kernel org>
- To: Mike Snitzer <snitzer redhat com>
- Cc: k-ueda ct jp nec com, jaxboe fusionio com, jamie shareable org, linux-kernel vger kernel org, linux-raid vger kernel org, linux-fsdevel vger kernel org, dm-devel redhat com, j-nomura ce jp nec com, hch lst de
- Subject: Re: [dm-devel] [PATCH 2/5] dm: implement REQ_FLUSH/FUA support for bio-based dm
- Date: Wed, 01 Sep 2010 15:56:09 +0200
On 09/01/2010 03:54 PM, Mike Snitzer wrote:
>> It just doesn't happen anymore. If the underlying device doesn't
>> support FLUSH/FUA, the block layer simply make those parts noop. IOW,
>> it no longer distinguishes between writeback cache which doesn't
>> support cache flush at all and writethrough cache. Devices which have
>> WB cache w/o flush very difficult to come by these days and there's
>> nothing much we can do anyway, so it doesn't make sense to require
>> everyone to implement -EOPNOTSUPP.
>>
>> One scheduled feature is to implement falling back to REQ_FLUSH when
>> the device advertises REQ_FUA but fails to process it, but one way or
>> the other, the goal is encapsulating REQ_FLUSH/FUA support in block
>> layer proper. If FLUSH/FUA can be retried using a different strategy,
>> it should be done inside request_queue proper instead of pushing retry
>> logic to all its users.
>
> OK, so maybe add this info to the patch header one of the primary
> FLUSH+FUA conversion patches?
Sure.
Thanks.
--
tejun
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]