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 1/2] rbd: RBD_DEV_FLAG_THICK rbd_dev_flags bit
Date: Mon, 19 Mar 2018 21:01:06 +0900 [thread overview]
Message-ID: <5AAFA682.2080901@hitachi.com> (raw)
This patch adds a user interface to prevent from issuing discard
requests onto the specified rbd device. This is needed for
thick-provisioned images. To avoid discarding allocated blocks on
thick-provision image, users can specify this flag bit via sysfs
(/sys/bus/rbd/devices/<dev-id>/thick).
When users write "1" to the file, rbd doesn't issue discard
operation; meanwhile, if users write "0" to the file then rbd
issues discard operation.
Signed-off-by: Hitoshi Kamei <hitoshi.kamei.xm@hitachi.com>
Cc: Mitsuo Hayasaka <mitsuo.hayasaka.hu@hitachi.com>
---
drivers/block/rbd.c | 38 ++++++++++++++++++++++++++++++++++++++
1 file changed, 38 insertions(+)
diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
index 8e40da093766..dba60ef43a47 100644
--- a/drivers/block/rbd.c
+++ b/drivers/block/rbd.c
@@ -427,6 +427,7 @@ enum rbd_dev_flags {
RBD_DEV_FLAG_EXISTS, /* mapped snapshot has not been deleted */
RBD_DEV_FLAG_REMOVING, /* this mapping is being removed */
RBD_DEV_FLAG_BLACKLISTED, /* our ceph_client is blacklisted */
+ RBD_DEV_FLAG_THICK, /* image is thick-provisioned */
};
static DEFINE_MUTEX(client_mutex); /* Serialize client creation */
@@ -4011,6 +4012,15 @@ static void rbd_queue_workfn(struct work_struct *work)
goto err;
}
+ /* Ignore/skip discard requests for thick-provision image */
+
+ if (op_type == OBJ_OP_DISCARD &&
+ test_bit(RBD_DEV_FLAG_THICK, &rbd_dev->flags)) {
+ dout("%s: Ignored a discard request\n", __func__);
+ result = 0;
+ goto err_rq;
+ }
+
/* Ignore/skip any zero-length requests */
if (!length) {
@@ -4600,6 +4610,32 @@ static ssize_t rbd_image_refresh(struct device *dev,
return size;
}
+static ssize_t rbd_thick_store(struct device *dev,
+ struct device_attribute *attr,
+ const char *buf,
+ size_t size)
+{
+ struct rbd_device *rbd_dev = dev_to_rbd_dev(dev);
+
+ spin_lock_irq(&rbd_dev->lock);
+ if (!strncmp(buf, "1", size))
+ set_bit(RBD_DEV_FLAG_THICK, &rbd_dev->flags);
+ else if (!strncmp(buf, "0", size))
+ clear_bit(RBD_DEV_FLAG_THICK, &rbd_dev->flags);
+ spin_unlock_irq(&rbd_dev->lock);
+
+ return size;
+}
+
+static ssize_t rbd_thick_show(struct device *dev,
+ struct device_attribute *attr, char *buf)
+{
+ struct rbd_device *rbd_dev = dev_to_rbd_dev(dev);
+ int is_thick = test_bit(RBD_DEV_FLAG_THICK, &rbd_dev->flags) ? 1 : 0;
+
+ return sprintf(buf, "%d\n", is_thick);
+}
+
static DEVICE_ATTR(size, S_IRUGO, rbd_size_show, NULL);
static DEVICE_ATTR(features, S_IRUGO, rbd_features_show, NULL);
static DEVICE_ATTR(major, S_IRUGO, rbd_major_show, NULL);
@@ -4616,6 +4652,7 @@ static DEVICE_ATTR(refresh, S_IWUSR, NULL, rbd_image_refresh);
static DEVICE_ATTR(current_snap, S_IRUGO, rbd_snap_show, NULL);
static DEVICE_ATTR(snap_id, S_IRUGO, rbd_snap_id_show, NULL);
static DEVICE_ATTR(parent, S_IRUGO, rbd_parent_show, NULL);
+static DEVICE_ATTR(thick, 0644, rbd_thick_show, rbd_thick_store);
static struct attribute *rbd_attrs[] = {
&dev_attr_size.attr,
@@ -4634,6 +4671,7 @@ static struct attribute *rbd_attrs[] = {
&dev_attr_snap_id.attr,
&dev_attr_parent.attr,
&dev_attr_refresh.attr,
+ &dev_attr_thick.attr,
NULL
};
--
2.15.1
next reply other threads:[~2018-03-19 12:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 12:01 KAMEI Hitoshi [this message]
[not found] ` <5AB0E4F3.8090108@easystack.cn>
2018-03-22 11:57 ` Re: [PATCH 1/2] rbd: RBD_DEV_FLAG_THICK rbd_dev_flags bit 亀井仁志 / KAMEI,HITOSHI
2018-03-23 9:31 ` Ilya Dryomov
2018-03-23 9:34 ` Ilya Dryomov
2018-03-26 12:31 ` 亀井仁志 / KAMEI,HITOSHI
2018-03-26 13:24 ` Ilya Dryomov
2018-03-27 9:44 ` KAMEI Hitoshi
2018-03-27 16:27 ` Ilya Dryomov
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=5AAFA682.2080901@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;
as well as URLs for NNTP newsgroup(s).