write barrier in RAID5

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I can see how FUA is handled, but REQ_FLUSH seems problematic. My understanding of REQ_FLUSH semantics: all requests before the flush request must *complete* before the flush request complete. For IO remap layer like MD, we need to guarantee all previous requests are *submitted* to component devices before submitting the flush request. Is that correct?

If so why I don't see the code which make sure the pending write requests in stripe cache are processed & submitted before submit_flushes() get called? Thanks

Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux