|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH] libxl: introduce an option for disabling the non-O_DIRECT workaround
On 11/26/2013 05:46 PM, Konrad Rzeszutek Wilk wrote: On Tue, Nov 26, 2013 at 11:42:31AM +0000, Ian Jackson wrote:From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> Document and implement a new option that permits disk backends which would otherwise have to avoid O_DIRECT (because of the network memory lifetime bug) to use it anyway. This is: Not everyone builds her own kernel from the latest release; until we can be relatively sure that this fix has hit distros (including older LTS-style ones), we have to deal with the fact that the O_DIRECT bug may be present. The purpose of this flag is to enable you to turn it on when you know it's safe -- for instance, if you're running a kernel with this changeset. It is worth asking the question now though: Given that this has been checked in, would it make sense to switch the polarity of this -- default to O_DIRECT on and have a flag to allow people to switch it off? If not now, maybe for 4.5? And in that case, maybe we should change the argument to be tristate: default, true, or false (i.e., true means I know it's safe, false means I know it's unsafe, default means I haven't specified either way)? -George _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |