From: Josh Durgin <josh.durgin@inktank.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: RBD trim / unmap support?
Date: Thu, 01 Nov 2012 16:36:44 -0700 [thread overview]
Message-ID: <5093078C.4020404@inktank.com> (raw)
In-Reply-To: <509306CC.5080307@profihost.ag>
On 11/01/2012 04:33 PM, Stefan Priebe wrote:
> Hello list,
>
> does rbd support trim / unmap? Or is it planned to support it?
>
> Greets,
> Stefan
librbd (and thus qemu) support it. The rbd kernel module does not yet.
See http://ceph.com/docs/master/rbd/qemu-rbd/#enabling-discard-trim
Josh
next prev parent reply other threads:[~2012-11-01 23:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 23:33 RBD trim / unmap support? Stefan Priebe
2012-11-01 23:36 ` Josh Durgin [this message]
2012-11-02 8:20 ` Stefan Priebe - Profihost AG
2012-11-02 8:21 ` Dietmar Maurer
2012-11-02 9:08 ` Stefan Priebe - Profihost AG
2012-11-02 14:18 ` Stefan Priebe - Profihost AG
2012-11-02 16:16 ` Josh Durgin
2012-11-02 20:13 ` Stefan Priebe
2012-11-03 18:47 ` Stefan Priebe
2012-11-06 8:09 ` Stefan Priebe - Profihost AG
2012-11-06 22:45 ` Stefan Priebe
2012-11-11 12:08 ` Stefan Priebe
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=5093078C.4020404@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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