From: Alex Elder <elder@inktank.com>
To: ceph-devel@vger.kernel.org
Subject: [PATCH] rbd: kill rbd_init_watch_dev()
Date: Thu, 26 Jul 2012 14:11:18 -0500 [thread overview]
Message-ID: <50119656.9080709@inktank.com> (raw)
When an rbd image is mapped, a watch request is issued so that the
client will get notified in the event the image header object
changes. This is done using rbd_init_watch_dev(), which calls
rbd_req_sync_watch().
rbd_init_watch_dev() is organized as a loop, arranging to re-issue
the request after refreshing the header if -ERANGE ever gets
returned. But the only way rbd_req_sync_watch() will return -ERANGE
is if the CEPH_OSD_OP_WATCH operation returns that, which it will
not.
As a result, the whole looping structure and in fact the whole
function becomes excessive. So get rid of rbd_init_watch_dev(),
and call rbd_req_sync_watch() directly in the one place it's used.
Signed-off-by: Alex Elder <elder@inktank.com>
---
drivers/block/rbd.c | 18 +-----------------
1 file changed, 1 insertion(+), 17 deletions(-)
diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
index 94d0745..71e3f3b 100644
--- a/drivers/block/rbd.c
+++ b/drivers/block/rbd.c
@@ -2191,22 +2191,6 @@ static void rbd_bus_del_dev(struct rbd_device
*rbd_dev)
device_unregister(&rbd_dev->dev);
}
-static int rbd_init_watch_dev(struct rbd_device *rbd_dev)
-{
- int ret, rc;
-
- do {
- ret = rbd_req_sync_watch(rbd_dev);
- if (ret == -ERANGE) {
- rc = rbd_refresh_header(rbd_dev, NULL);
- if (rc < 0)
- return rc;
- }
- } while (ret == -ERANGE);
-
- return ret;
-}
-
static atomic64_t rbd_id_max = ATOMIC64_INIT(0);
/*
@@ -2510,7 +2494,7 @@ static ssize_t rbd_add(struct bus_type *bus,
if (rc)
goto err_out_bus;
- rc = rbd_init_watch_dev(rbd_dev);
+ rc = rbd_req_sync_watch(rbd_dev);
if (rc)
goto err_out_bus;
--
1.7.9.5
next reply other threads:[~2012-07-26 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 19:11 Alex Elder [this message]
2012-07-30 21:46 ` [PATCH] rbd: kill rbd_init_watch_dev() Josh Durgin
2012-07-30 22:48 ` Alex Elder
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=50119656.9080709@inktank.com \
--to=elder@inktank.com \
--cc=ceph-devel@vger.kernel.org \
/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