From: Jeff Cody <jcody@redhat.com>
To: Josh Durgin <jdurgin@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/4] rbd: make qemu's cache setting override any ceph setting
Date: Tue, 30 Jun 2015 15:47:49 -0400 [thread overview]
Message-ID: <20150630194749.GF13877@localhost.localdomain> (raw)
In-Reply-To: <1433993326-26294-4-git-send-email-jdurgin@redhat.com>
On Wed, Jun 10, 2015 at 08:28:45PM -0700, Josh Durgin wrote:
> To be safe, when cache=none is used ceph settings should not be able
> to override it to turn on caching. This was previously possible with
> rbd_cache=true in the rbd device configuration or a ceph configuration
> file. Similarly, rbd settings could have turned off caching when qemu
> requested it, although this would just be a performance problem.
>
> Fix this by changing rbd's cache setting to match qemu after all other
> ceph settings have been applied.
>
> Signed-off-by: Josh Durgin <jdurgin@redhat.com>
> ---
> block/rbd.c | 24 ++++++++++++------------
> 1 file changed, 12 insertions(+), 12 deletions(-)
>
> diff --git a/block/rbd.c b/block/rbd.c
> index 50b5f6b..00d027d 100644
> --- a/block/rbd.c
> +++ b/block/rbd.c
> @@ -460,6 +460,18 @@ static int qemu_rbd_open(BlockDriverState *bs, QDict *options, int flags,
> s->snap = g_strdup(snap_buf);
> }
>
> + if (strstr(conf, "conf=") == NULL) {
> + /* try default location, but ignore failure */
> + rados_conf_read_file(s->cluster, NULL);
> + }
> +
> + if (conf[0] != '\0') {
> + r = qemu_rbd_set_conf(s->cluster, conf, errp);
> + if (r < 0) {
> + goto failed_shutdown;
> + }
> + }
> +
> /*
> * Fallback to more conservative semantics if setting cache
> * options fails. Ignore errors from setting rbd_cache because the
> @@ -473,18 +485,6 @@ static int qemu_rbd_open(BlockDriverState *bs, QDict *options, int flags,
> rados_conf_set(s->cluster, "rbd_cache", "true");
> }
>
> - if (strstr(conf, "conf=") == NULL) {
> - /* try default location, but ignore failure */
> - rados_conf_read_file(s->cluster, NULL);
> - }
> -
> - if (conf[0] != '\0') {
> - r = qemu_rbd_set_conf(s->cluster, conf, errp);
> - if (r < 0) {
> - goto failed_shutdown;
> - }
> - }
> -
> r = rados_connect(s->cluster);
> if (r < 0) {
> error_setg(errp, "error connecting");
> --
> 1.9.1
>
Reviewed-by: Jeff Cody <jcody@redhat.com>
next prev parent reply other threads:[~2015-06-30 19:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 3:28 [Qemu-devel] [PATCH 0/4] rbd cleanup and settings precedence fixes Josh Durgin
2015-06-11 3:28 ` [Qemu-devel] [PATCH 1/4] rbd: remove unused constants and fields Josh Durgin
2015-06-30 19:47 ` Jeff Cody
2015-06-11 3:28 ` [Qemu-devel] [PATCH 2/4] MAINTAINERS: update email address Josh Durgin
2015-06-30 19:47 ` Jeff Cody
2015-06-11 3:28 ` [Qemu-devel] [PATCH 3/4] rbd: make qemu's cache setting override any ceph setting Josh Durgin
2015-06-30 19:47 ` Jeff Cody [this message]
2015-06-11 3:28 ` [Qemu-devel] [PATCH 4/4] rbd: fix ceph settings precedence Josh Durgin
2015-06-30 18:28 ` [Qemu-devel] [PATCH 0/4] rbd cleanup and settings precedence fixes Josh Durgin
2015-07-09 9:59 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-07-14 14:20 ` Kevin Wolf
2015-07-14 19:42 ` Josh Durgin
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=20150630194749.GF13877@localhost.localdomain \
--to=jcody@redhat.com \
--cc=jdurgin@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).