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: Greg Farnum <greg@inktank.com>, ceph-devel@vger.kernel.org
Subject: Re: how to debug slow rbd block device
Date: Wed, 23 May 2012 09:22:50 +0200	[thread overview]
Message-ID: <4FBC904A.7090407@profihost.ag> (raw)
In-Reply-To: <4FBC8F8F.6060004@inktank.com>

Am 23.05.2012 09:19, schrieb Josh Durgin:
> On 05/23/2012 12:01 AM, Stefan Priebe - Profihost AG wrote:
> You can use any of the rbd-specific options (like rbd_cache_max_dirty)
> with qemu >= 0.15.
> 
> You can set them in a global ceph.conf file, or specify them on the qemu
> command line like:
> 
> qemu -m 512 -drive
> file=rbd:pool/image:rbd_cache_max_dirty=0:rbd_cache=true,format=raw,if=virtio
ah thanks and sorry. Is there a way to verify which options are active /
working on a specific rbd block device?

Stefan

  reply	other threads:[~2012-05-23  7:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 12:45 how to debug slow rbd block device Stefan Priebe - Profihost AG
2012-05-22 14:52 ` Andrey Korolyov
2012-05-22 19:27   ` Stefan Priebe
2012-05-22 19:35 ` Greg Farnum
2012-05-22 19:40   ` Stefan Priebe
2012-05-22 19:52     ` Greg Farnum
2012-05-22 20:13       ` Stefan Priebe
2012-05-22 20:30       ` Stefan Priebe
2012-05-22 20:48         ` Mark Nelson
2012-05-22 20:54           ` Stefan Priebe
2012-05-22 20:49         ` Greg Farnum
2012-05-22 21:00           ` Stefan Priebe
2012-05-22 21:11             ` Greg Farnum
2012-05-23  6:18               ` Stefan Priebe - Profihost AG
2012-05-23  6:30                 ` Josh Durgin
2012-05-23  7:01                   ` Stefan Priebe - Profihost AG
2012-05-23  7:19                     ` Josh Durgin
2012-05-23  7:22                       ` Stefan Priebe - Profihost AG [this message]
2012-05-23  7:33                         ` Josh Durgin
     [not found]                           ` <CABYiri8PXT9dpCGLE7dn=_PoW8CdLxqZF87OHe=dMXEWxogb_w@mail.gmail.com>
2012-05-23 19:54                             ` Josh Durgin
2012-05-23  8:20                       ` Stefan Priebe - Profihost AG
2012-05-23  8:29                         ` Josh Durgin
2012-05-23  7:22                   ` Andrey Korolyov
2012-05-23  8:15                     ` Stefan Priebe - Profihost AG
2012-05-23 11:47                     ` Mark Nelson
2012-05-23  8:30               ` Stefan Priebe - Profihost AG
2012-05-23  9:10                 ` Stefan Priebe - Profihost AG

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=4FBC904A.7090407@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=ceph-devel@vger.kernel.org \
    --cc=greg@inktank.com \
    --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