David Chinner wrote:
Barrier != synchronous write,
Of course. FYI, XFS only issues barriers on *async* writes.
But barrier semantics - as far as they've been described by everyone
but you indicate that the barrier write is guaranteed to be on stable
storage when it returns.
Hrm... I may have misunderstood the perspective you were talking from.
Yes, when the bio is completed it must be on the media, but the
filesystem should issue both requests, and then really not care when
they complete. That is to say, the filesystem should not wait for block
A to finish before issuing block B; it should issue both, and use
barriers to make sure they hit the disk in the correct order.
XFS relies on the block being stable before any other write
goes to disk. That is the semantic that the barrier I/Os currently
have. How that is implemented in the device is irrelevant to me,
but if I issue a barrier I/O, I do not expect *any* I/O to be
reordered around it.
Right... it just needs to control the order of the requests, just not
wait on one to finish before issuing the next.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
- Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
- Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
- Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
- Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
