From: KAMEI Hitoshi <hitoshi.kamei.xm@hitachi.com>
To: idryomov@gmail.com, sage@redhat.com, elder@kernel.org,
ceph-devel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] rbd: thick-provision image support
Date: Mon, 19 Mar 2018 21:00:33 +0900 [thread overview]
Message-ID: <5AAFA661.60103@hitachi.com> (raw)
This patch series adds the thick-provision image support to
/drivers/block/rbd.c relating to https://github.com/ceph/ceph/pull/18317.
The rbd will not issue the discard operation to thick-provision
images, if applied.
The rbd should not discard any allocated blocks of thick-provision
image to ensure writing data to rbd images. So this patch
prevents from discarding allocated blocks on thick-provision
image.
This patch series creates sysfs file to manipulate thick-provision
status. If users write "1" to /sys/bus/rbd/devices/<dev-id>/thick,
then the image is changed to thick-provision image. And if users
write "0" to it, then the image is changed to thin-provision
image. I will add the code changing status for the rbd map command.
Hitoshi Kamei (2):
rbd: RBD_DEV_FLAG_THICK rbd_dev_flags bit
rbd: add 'thick' sysfs rbd device attribute
Documentation/ABI/testing/sysfs-bus-rbd | 6 ++++++
drivers/block/rbd.c | 37 +++++++++++++++++++++++++++++++++
2 files changed, 43 insertions(+)
--
2.15.1
next reply other threads:[~2018-03-19 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 12:00 KAMEI Hitoshi [this message]
2018-03-20 14:06 ` [PATCH 0/2] rbd: thick-provision image support Ilya Dryomov
2018-03-20 22:31 ` Jason Dillaman
2018-03-22 11:59 ` 亀井仁志 / KAMEI,HITOSHI
2018-03-22 11:58 ` 亀井仁志 / KAMEI,HITOSHI
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=5AAFA661.60103@hitachi.com \
--to=hitoshi.kamei.xm@hitachi.com \
--cc=ceph-devel@vger.kernel.org \
--cc=elder@kernel.org \
--cc=idryomov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sage@redhat.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