On Thu, May 31 2007, Phillip Susi wrote:
> David Chinner wrote:
> >That sounds like a good idea - we can leave the existing
> >WRITE_BARRIER behaviour unchanged and introduce a new WRITE_ORDERED
> >behaviour that only guarantees ordering. The filesystem can then
> >choose which to use where appropriate....
>
> So what if you want a synchronous write, but DON'T care about the order?
> They need to be two completely different flags which you can choose
> to combine, or use individually.
If you have a use case for that, we can easily support it as well...
Depending on the drive capabilities (FUA support or not), it may be
nearly as slow as a "real" barrier write.
--
Jens Axboe
-
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:
- 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.
- 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.
- 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]