Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.

Jens Axboe wrote:

No Stephan is right, the barrier is both an ordering and integrity
constraint. If a driver completes a barrier request before that request
and previously submitted requests are on STABLE storage, then it
violates that principle. Look at the code and the various ordering
options.

I am saying that is the wrong thing to do. Barrier should be about ordering only. So long as the order they hit the media is maintained, the order the requests are completed in can change. barrier.txt bears this out:

"Requests in ordered sequence are issued in order, but not required to finish in order. Barrier implementation can handle out-of-order completion of ordered sequence. IOW, the requests MUST be processed in order but the hardware/software completion paths are allowed to reorder completion notifications - eg. current SCSI midlayer doesn't preserve completion order during error handling."

-
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/

---

• Follow-Ups:
  • Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
    • From: Jens Axboe <[email protected]>

• References:
  • [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
    • From: Neil Brown <[email protected]>
  • Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
    • From: Neil Brown <[email protected]>
  • Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
    • From: David Chinner <[email protected]>
  • Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
    • From: Phillip Susi <[email protected]>
  • Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
    • From: David Chinner <[email protected]>
  • Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
    • From: Phillip Susi <[email protected]>
  • Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
    • From: Phillip Susi <[email protected]>
  • Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
    • From: Jens Axboe <[email protected]>

• Prev by Date: Re: [PATCH] Introduce O_CLOEXEC (take >2)
• Next by Date: Re: 2.6.22-rc3-mm1
• Previous by thread: Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
• Next by thread: Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
• Index(es):
  • Date
  • Thread

[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]