CEPH filesystem development
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Josh Durgin <josh.durgin@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: difference between qemu cache settings and ceph.conf rbd cache settings?
Date: Tue, 19 Jun 2012 08:44:52 +0200	[thread overview]
Message-ID: <4FE01FE4.6070200@profihost.ag> (raw)
In-Reply-To: <4FE01F6E.50200@inktank.com>

Am 19.06.2012 08:42, schrieb Josh Durgin:
> In qemu, the cache settings map to:
>
> writeback:
> rbd_cache = true
>
> writethrough:
> rbd_cache = true
> rbd_cache_max_dirty = 0
>
> none:
> rbd_cache = false
>
> qemu's settings are overridden by any custom settings you have in a
> config file or on the qemu command line.

Thanks!

Stefan

      reply	other threads:[~2012-06-19  6:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19  6:37 difference between qemu cache settings and ceph.conf rbd cache settings? Stefan Priebe - Profihost AG
2012-06-19  6:42 ` Josh Durgin
2012-06-19  6:44   ` Stefan Priebe - Profihost AG [this message]

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=4FE01FE4.6070200@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=ceph-devel@vger.kernel.org \
    --cc=josh.durgin@inktank.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox