From: Alex Elder <elder@ieee.org>
To: Ilya Dryomov <idryomov@gmail.com>, ceph-devel@vger.kernel.org
Subject: Re: [PATCH 3/3] rbd: queue_depth map option
Date: Thu, 25 Jun 2015 09:24:48 -0500 [thread overview]
Message-ID: <558C0F30.6050907@ieee.org> (raw)
In-Reply-To: <1435223480-35238-4-git-send-email-idryomov@gmail.com>
On 06/25/2015 04:11 AM, Ilya Dryomov wrote:
> nr_requests (/sys/block/rbd<id>/queue/nr_requests) is pretty much
> irrelevant in blk-mq case because each driver sets its own max depth
> that it can handle and that's the number of tags that gets preallocated
> on setup. Users can't increase queue depth beyond that value via
> writing to nr_requests.
>
> For rbd we are happy with the default BLKDEV_MAX_RQ (128) for most
> cases but we want to give users the opportunity to increase it.
> Introduce a new per-device queue_depth option to do just that:
>
> $ sudo rbd map -o queue_depth=1024 ...
>
> Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
I haven't gone to follow through what happens with this
but I assume a value that's too large will be caught when
it's attempted to be used or something.
In any case this looks good to me.
Reviewed-by: Alex Elder <elder@linaro.org>
> ---
> drivers/block/rbd.c | 17 ++++++++++++++---
> 1 file changed, 14 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
> index e502bce02d2c..b316ee48a30b 100644
> --- a/drivers/block/rbd.c
> +++ b/drivers/block/rbd.c
> @@ -728,6 +728,7 @@ static struct rbd_client *rbd_client_find(struct ceph_options *ceph_opts)
> * (Per device) rbd map options
> */
> enum {
> + Opt_queue_depth,
> Opt_last_int,
> /* int args above */
> Opt_last_string,
> @@ -738,6 +739,7 @@ enum {
> };
>
> static match_table_t rbd_opts_tokens = {
> + {Opt_queue_depth, "queue_depth=%d"},
> /* int args above */
> /* string args above */
> {Opt_read_only, "read_only"},
> @@ -748,9 +750,11 @@ static match_table_t rbd_opts_tokens = {
> };
>
> struct rbd_options {
> + int queue_depth;
> bool read_only;
> };
>
> +#define RBD_QUEUE_DEPTH_DEFAULT BLKDEV_MAX_RQ
> #define RBD_READ_ONLY_DEFAULT false
>
> static int parse_rbd_opts_token(char *c, void *private)
> @@ -774,6 +778,13 @@ static int parse_rbd_opts_token(char *c, void *private)
> }
>
> switch (token) {
> + case Opt_queue_depth:
> + if (intval < 1) {
> + pr_err("queue_depth out of range\n");
> + return -EINVAL;
> + }
> + rbd_opts->queue_depth = intval;
> + break;
> case Opt_read_only:
> rbd_opts->read_only = true;
> break;
> @@ -3761,10 +3772,9 @@ static int rbd_init_disk(struct rbd_device *rbd_dev)
>
> memset(&rbd_dev->tag_set, 0, sizeof(rbd_dev->tag_set));
> rbd_dev->tag_set.ops = &rbd_mq_ops;
> - rbd_dev->tag_set.queue_depth = BLKDEV_MAX_RQ;
> + rbd_dev->tag_set.queue_depth = rbd_dev->opts->queue_depth;
> rbd_dev->tag_set.numa_node = NUMA_NO_NODE;
> - rbd_dev->tag_set.flags =
> - BLK_MQ_F_SHOULD_MERGE | BLK_MQ_F_SG_MERGE;
> + rbd_dev->tag_set.flags = BLK_MQ_F_SHOULD_MERGE | BLK_MQ_F_SG_MERGE;
> rbd_dev->tag_set.nr_hw_queues = 1;
> rbd_dev->tag_set.cmd_size = sizeof(struct work_struct);
>
> @@ -4948,6 +4958,7 @@ static int rbd_add_parse_args(const char *buf,
> goto out_mem;
>
> rbd_opts->read_only = RBD_READ_ONLY_DEFAULT;
> + rbd_opts->queue_depth = RBD_QUEUE_DEPTH_DEFAULT;
>
> copts = ceph_parse_options(options, mon_addrs,
> mon_addrs + mon_addrs_size - 1,
>
next prev parent reply other threads:[~2015-06-25 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 9:11 [PATCH 0/3] rbd: queue_depth map option Ilya Dryomov
2015-06-25 9:11 ` [PATCH 1/3] rbd: terminate rbd_opts_tokens with Opt_err Ilya Dryomov
2015-06-25 14:22 ` Alex Elder
2015-06-25 9:11 ` [PATCH 2/3] rbd: store rbd_options in rbd_device Ilya Dryomov
2015-06-25 14:23 ` Alex Elder
2015-06-25 9:11 ` [PATCH 3/3] rbd: queue_depth map option Ilya Dryomov
2015-06-25 14:24 ` Alex Elder [this message]
2015-06-25 14:31 ` 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=558C0F30.6050907@ieee.org \
--to=elder@ieee.org \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.