Re: vioif vs if_vio

2016-09-24 Thread Paul Goyette
On Sat, 24 Sep 2016, Thor Lancelot Simon wrote: On Sat, Sep 24, 2016 at 02:02:16PM +0800, Paul Goyette wrote: Shouldn't the vioif(4) device be more properly named if_vio(4), to be consistent with other network interfaces? I think the code was imported with the same filenames as its original s

Re: Plan: journalling fixes for WAPBL

2016-09-24 Thread Warner Losh
On Sat, Sep 24, 2016 at 2:01 AM, David Holland wrote: > On Fri, Sep 23, 2016 at 07:51:32PM +0200, Manuel Bouyer wrote: > > > > *if you have the write cache disabled* > > > > > > *Running with the write cache enabled is a bad idea* > > > > On ATA devices, you can't permanently disable the writ

Re: vioif vs if_vio

2016-09-24 Thread Thor Lancelot Simon
On Sat, Sep 24, 2016 at 02:02:16PM +0800, Paul Goyette wrote: > Shouldn't the vioif(4) device be more properly named if_vio(4), to be > consistent with other network interfaces? I think the code was imported with the same filenames as its original source, to ease merging of updates. > With its cu

Re: FUA and TCQ (was: Plan: journalling fixes for WAPBL)

2016-09-24 Thread Thor Lancelot Simon
On Fri, Sep 23, 2016 at 01:02:26PM +, paul.kon...@dell.com wrote: > > > On Sep 23, 2016, at 5:49 AM, Edgar Fu?? wrote: > > > >> The whole point of tagged queueing is to let you *not* set [the write > >> cache] bit in the mode pages and still get good performance. > > I don't get that. My un

Re: Plan: journalling fixes for WAPBL

2016-09-24 Thread David Holland
On Fri, Sep 23, 2016 at 07:51:32PM +0200, Manuel Bouyer wrote: > > > *if you have the write cache disabled* > > > > *Running with the write cache enabled is a bad idea* > > On ATA devices, you can't permanently disable the write cache. You have > to do it on every power cycles. There are a