nvmet: use unlikely for req status check
authorChaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Mon, 19 Nov 2018 21:35:30 +0000 (13:35 -0800)
committerJens Axboe <axboe@kernel.dk>
Sat, 8 Dec 2018 05:26:58 +0000 (22:26 -0700)
This patch adds unlikely in the nvmet request completion path for the
status check in the low level function __nvmet_req_complete.
This is helpful in the scenario where host and target connection is
working smoothly.

Signed-off-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
drivers/nvme/target/core.c

index 2df70010e9f29224dc5f3e28bf1c071ed94c4f0e..e468100b9211f26b800ed9e7960b5a279e41a370 100644 (file)
@@ -617,7 +617,7 @@ static void __nvmet_req_complete(struct nvmet_req *req, u16 status)
                nvmet_update_sq_head(req);
        req->rsp->sq_id = cpu_to_le16(req->sq->qid);
        req->rsp->command_id = req->cmd->common.command_id;
-       if (status)
+       if (unlikely(status))
                nvmet_set_status(req, status);
        if (req->ns)
                nvmet_put_namespace(req->ns);