Re: SuSE O_DIRECT|O_NONBLOCK overload

2014-03-14 Thread Mike Christie
On 03/12/2014 07:15 PM, NeilBrown wrote: > I also think there should probably be just one FAILFAST flag. Where it was > the DEV or the TRANSPORT or the DRIVER that failed could be returned in the > error code for any caller that cared. But as I don't know why the one became > three I could well b

Re: SuSE O_DIRECT|O_NONBLOCK overload

2014-03-12 Thread NeilBrown
On Wed, 12 Mar 2014 04:00:15 -0700 Christoph Hellwig wrote: > The SLES12 tree has various patches to implement special > O_DIRECT|O_NONBLOCK semantics for block devices: > > > https://gitorious.org/opensuse/kernel-source/source/806eab3e4b02e798c1ae942440051f81c822ca35:patches.suse/block-n

SuSE O_DIRECT|O_NONBLOCK overload

2014-03-12 Thread Christoph Hellwig
The SLES12 tree has various patches to implement special O_DIRECT|O_NONBLOCK semantics for block devices: https://gitorious.org/opensuse/kernel-source/source/806eab3e4b02e798c1ae942440051f81c822ca35:patches.suse/block-nonblock-causes-failfast this seems genuinely useful and I'd be really