From: Chaitanya Kulkarni <kch@nvidia.com>
To: <linux-block@vger.kernel.org>
Cc: <axboe@kernel.dk>, <ming.lei@redhat.com>,
<shinichiro.kawasaki@wdc.com>, <damien.lemoal@wdc.com>,
Chaitanya Kulkarni <kch@nvidia.com>
Subject: [PATCH 1/2] null_blk: remove hardcoded alloc_cmd() parameter
Date: Wed, 16 Feb 2022 01:30:19 -0800 [thread overview]
Message-ID: <20220216093020.175351-2-kch@nvidia.com> (raw)
In-Reply-To: <20220216093020.175351-1-kch@nvidia.com>
Only caller of alloc_cmd() is null_submit_bio() unconditionally sets
second parameter to true & that is statically hard-coded in null_blk.
There is no point in having statically hardcoded function parameter.
Remove the unnecessary parameter can_wait and adjust the code so it
can retain existing behavior of waiting when we don't get valid
nullb_cmd from __alloc_cmd() in alloc_cmd().
The restructured code avoids multiple return statements, multiple
calls to __alloc_cmd() and resulting a fast path call to
prepare_to_wait() due to removal of first alloc_cmd() call.
Signed-off-by: Chaitanya Kulkarni <kch@nvidia.com>
---
drivers/block/null_blk/main.c | 21 +++++++++------------
1 file changed, 9 insertions(+), 12 deletions(-)
diff --git a/drivers/block/null_blk/main.c b/drivers/block/null_blk/main.c
index 13004beb48ca..d78fc3edb22e 100644
--- a/drivers/block/null_blk/main.c
+++ b/drivers/block/null_blk/main.c
@@ -719,26 +719,23 @@ static struct nullb_cmd *__alloc_cmd(struct nullb_queue *nq)
return NULL;
}
-static struct nullb_cmd *alloc_cmd(struct nullb_queue *nq, int can_wait)
+static struct nullb_cmd *alloc_cmd(struct nullb_queue *nq)
{
struct nullb_cmd *cmd;
DEFINE_WAIT(wait);
- cmd = __alloc_cmd(nq);
- if (cmd || !can_wait)
- return cmd;
-
do {
- prepare_to_wait(&nq->wait, &wait, TASK_UNINTERRUPTIBLE);
+ /*
+ * This avoids multiple return statements, multiple calls to
+ * __alloc_cmd() and a fast path call to prepare_to_wait().
+ */
cmd = __alloc_cmd(nq);
if (cmd)
- break;
-
+ return cmd;
+ prepare_to_wait(&nq->wait, &wait, TASK_UNINTERRUPTIBLE);
io_schedule();
+ finish_wait(&nq->wait, &wait);
} while (1);
-
- finish_wait(&nq->wait, &wait);
- return cmd;
}
static void end_cmd(struct nullb_cmd *cmd)
@@ -1478,7 +1475,7 @@ static void null_submit_bio(struct bio *bio)
struct nullb_queue *nq = nullb_to_queue(nullb);
struct nullb_cmd *cmd;
- cmd = alloc_cmd(nq, 1);
+ cmd = alloc_cmd(nq);
cmd->bio = bio;
null_handle_cmd(cmd, sector, nr_sectors, bio_op(bio));
--
2.29.0
next prev parent reply other threads:[~2022-02-16 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 9:30 [PATCH 0/2] null_blk: cleanup alloc_cmd() Chaitanya Kulkarni
2022-02-16 9:30 ` Chaitanya Kulkarni [this message]
2022-02-16 10:19 ` [PATCH 1/2] null_blk: remove hardcoded alloc_cmd() parameter Damien Le Moal
2022-02-16 9:30 ` [PATCH 2/2] null_blk: remove local var & init cmd in alloc_cmd Chaitanya Kulkarni
2022-02-16 10:23 ` Damien Le Moal
2022-02-16 17:35 ` Chaitanya Kulkarni
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=20220216093020.175351-2-kch@nvidia.com \
--to=kch@nvidia.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=shinichiro.kawasaki@wdc.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