All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH v2] introduce a cache options for PV disks
Date: Thu, 27 Jun 2013 17:58:51 +0100	[thread overview]
Message-ID: <1372352331.8976.51.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <20940.28013.656000.329381@mariner.uk.xensource.com>

On Thu, 2013-06-27 at 17:50 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [PATCH v2] introduce a cache options for PV disks"):
> > I think I can parse it now. It doesn't really say what the option does
> > though. I'd expect it to say something about "disabling the workaround"
> > or "the backend may use O_DIRECT".
> 
> How about:

Sounds good thanks.

> 
>  * direct-io-safe
>  *      Values:         0/1 (boolean)
>  *      Default Value:  0
>  *
>  *      The underlying storage is not affected by the direct IO memory
>  *      lifetime bug.  See:
>  *        http://lists.xen.org/archives/html/xen-devel/2012-12/msg01154.html
>  *
>  *      Therefore this option gives the backend permission to use
>  *      O_DIRECT, notwithstanding that bug.
>  *
>  *      That is, if this option is enabled, use of O_DIRECT is safe,
>  *      in circumstances where we would normally have avoided it as a
>  *      workaround for that bug.  This option is not relevant for all
>  *      backends, and even not necessarily supported for those for
>  *      which it is relevant.  A backend which knows that it is not
>  *      affected by the bug can ignore this option.
>  *
>  *      This option doesn't require a backend to use O_DIRECT, so it
>  *      should not be used to try to control the caching behaviour.
> 
> Ian.

  reply	other threads:[~2013-06-27 16:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 11:40 [PATCH v2] introduce a cache options for PV disks Stefano Stabellini
2013-06-27 14:21 ` Ian Jackson
2013-06-27 16:09   ` Ian Jackson
2013-06-27 16:24     ` Ian Campbell
2013-06-27 16:30       ` Ian Jackson
2013-06-27 16:34         ` Ian Jackson
2013-06-27 16:41           ` Ian Campbell
2013-06-27 16:50             ` Ian Jackson
2013-06-27 16:58               ` Ian Campbell [this message]
2013-06-27 16:41         ` Ian Campbell
2013-06-27 16:35       ` Ian Jackson
2013-06-27 16:20 ` Ian Jackson
2013-06-27 17:06   ` Stefano Stabellini
2013-06-27 17:13     ` Stefano Stabellini
2013-06-27 17:44     ` Ian Jackson
2013-06-27 17:50       ` Stefano Stabellini
2013-06-27 17:59         ` Ian Jackson
2013-06-27 18:01         ` Ian Jackson
2013-06-27 18:04           ` Ian Jackson
2013-06-28  7:39             ` Ian Campbell
2013-06-27 18:12           ` Stefano Stabellini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1372352331.8976.51.camel@zakaz.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.