CEPH filesystem development
 help / color / mirror / Atom feed
From: Josh Durgin <josh.durgin@inktank.com>
To: Mandell Degerness <mandell@pistoncloud.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: write-through cache
Date: Wed, 23 May 2012 17:44:11 -0700	[thread overview]
Message-ID: <4FBD845B.5030402@inktank.com> (raw)
In-Reply-To: <CA+jddaPW1YpHqo667dD6_9ce8iRhQLOX911-dWKT+XRFMR3YGw@mail.gmail.com>

On 05/23/2012 04:44 PM, Mandell Degerness wrote:
> I would like to test the effect of using the new write-through cache
> on RBD volumes mounted to Openstack VMs.  What, precisely, are the
> changes I need to make to the volume XML in order to do so?

If your only volumes are rbd, you can append 
:rbd_cache=true:rbd_cache_max_dirty=0 to the image name in the volume 
xml, so it would include something like

<source protocol="rbd" 
name="pool/image:rbd_cache=true:rbd_cache_max_dirty=0">

Josh

      reply	other threads:[~2012-05-24  0:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23 23:44 write-through cache Mandell Degerness
2012-05-24  0:44 ` Josh Durgin [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=4FBD845B.5030402@inktank.com \
    --to=josh.durgin@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=mandell@pistoncloud.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