nvme-multipath: fix io accounting on failover
PATCH 1/1 nvme-multipath: fix io accounting on failover
From: Keith Busch <[email protected]>
There are io stats accounting that needs to be handled, so don't call blk_mq_end_request() directly. Use the existing nvme_end_req() helper that already handles everything.
--- drivers/nvme/host/core.c | 2 +- drivers/nvme/host/multipath.c | 3 ++- drivers/nvme/host/nvme.h | 1 + 3 files changed, 4 insertions(+), 2 deletions(-)
drivers/nvme/host/core.c +1 -1
@@ -422,7 +422,7 @@ static inline void __nvme_end_req(struct request *req)nvme_mpath_end_request (req); } -static inline void nvme_end_req (struct request *req) +void nvme_end_req (struct request *req) {blk_status_t status =nvme_error_status (nvme_req (req)->status);
drivers/nvme/host/multipath.c +2 -1
@@ -118,7 +118,8 @@ void nvme_failover_req(struct request *req)blk_steal_bios (&ns->head->requeue_list, req);spin_unlock_irqrestore (&ns->head->requeue_lock, flags); -blk_mq_end_request (req,0 ); +nvme_req (req)->status =0 ; +nvme_end_req (req);kblockd_schedule_work (&ns->head->requeue_work); }
drivers/nvme/host/nvme.h +1 -0
@@ -767,6 +767,7 @@ static inline bool nvme_state_terminal(struct nvme_ctrl *ctrl) } } +void nvme_end_req (struct request *req);void nvme_complete_rq (struct request *req);void nvme_complete_batch_req (struct request *req);
Signature · 1 line
2.43.0
Awesome. I've noticed that there is an iostat bug lurking someplace during my many days of io policy testing these last two weeks. I'll add this patch to my test build and let you know if it fixes the problem!
/John
On 5/21/24 14:07, Keith Busch wrote:> From: Keith Busch <[email protected]>
Quoted 52 lines
There are io stats accounting that needs to be handled, so don't call
blk_mq_end_request()directly. Use the existingnvme_end_req()helper that already handles everything.Fixes d4d957b53d91ee ("nvme-multipath: support io stats on the mpath device")Signed-off-by Keith Busch <[email protected]>--- drivers/nvme/host/core.c | 2 +- drivers/nvme/host/multipath.c | 3 ++- drivers/nvme/host/nvme.h | 1 + 3 files changed, 4 insertions(+), 2 deletions(-)drivers/nvme/host/core.c +1
-1@@ -422,7 +422,7 @@ static inline void __nvme_end_req(struct request *req)nvme_mpath_end_request (req); } -static inline void nvme_end_req (struct request *req) +void nvme_end_req (struct request *req) {blk_status_t status =nvme_error_status (nvme_req (req)->status);drivers/nvme/host/multipath.c +2
-1@@ -118,7 +118,8 @@ void nvme_failover_req(struct request *req)blk_steal_bios (&ns->head->requeue_list, req);spin_unlock_irqrestore (&ns->head->requeue_lock, flags); -blk_mq_end_request (req,0 ); +nvme_req (req)->status =0 ; +nvme_end_req (req);kblockd_schedule_work (&ns->head->requeue_work); }drivers/nvme/host/nvme.h +1
-0@@ -767,6 +767,7 @@ static inline bool nvme_state_terminal(struct nvme_ctrl *ctrl) } } +void nvme_end_req (struct request *req);void nvme_complete_rq (struct request *req);void nvme_complete_batch_req (struct request *req);
Keith Busch
maintainerQuoted 3 lines · John Meneghini
Awesome. I've noticed that there is an iostat bug lurking someplace during my many days of io policy testing these last two weeks. I'll add this patch to my test build and let you know if it fixes the problem!
I was testing CMIC capable PCI devices. The nvme-pci driver is currently the only one batching completions, and that had a different multipath accounting bug. I had to fix that before I could validate this patch, and this one has a dependency on that first fix, which is here:
Looks good:
Quoted 6 lines · Keith Busch
From: Keith Busch <[email protected]>
There are io stats accounting that needs to be handled, so don't call
blk_mq_end_request()directly. Use the existingnvme_end_req()helper that already handles everything.
The changes look good however I have a question about why do we retry an IO when that IO is cancelled? For instance, when a multipath IO request is cancelled (from nvme_cancel_request()) we re-queue the bio in nvme_failover_req(). Similarly, for non-multipath request, we do retry request in nvme_retry_req() until retries for a request are maxed out by nvme_max_retries. So wouldn't it be appropriate to drop the cancelled request instead of retrying?
However, I do understand retrying a request on a different path when we got the request completion status specifying the path related error.
Thanks,
--Nilay
Keith Busch
maintainerQuoted 16 lines · Nilay Shroff
Quoted 6 lines · Keith Busch
From: Keith Busch <[email protected]>
There are io stats accounting that needs to be handled, so don't call
blk_mq_end_request()directly. Use the existingnvme_end_req()helper that already handles everything.The changes look good however I have a question about why do we retry an IO when that IO is cancelled? For instance, when a multipath IO request is cancelled (from
nvme_cancel_request()) we re-queue the bio innvme_failover_req(). Similarly, for non-multipath request, we do retry request innvme_retry_req()until retries for a request are maxed out bynvme_max_retries. So wouldn't it be appropriate to drop the cancelled request instead of retrying?
Quoted 2 lines
However, I do understand retrying a request on a different path when we got the request completion status specifying the path related error.
A cancelled request just means the host thinks the target failed to produce a response. It doesn't mean the host stopped caring about the command; the host still wants it to succeed, but determined corrective action is needed to reclaim and resubmit the command.
Quoted 17 lines · Keith Busch
Quoted 16 lines · Nilay Shroff
Quoted 6 lines · Keith Busch
From: Keith Busch <[email protected]>
There are io stats accounting that needs to be handled, so don't call
blk_mq_end_request()directly. Use the existingnvme_end_req()helper that already handles everything.The changes look good however I have a question about why do we retry an IO when that IO is cancelled? For instance, when a multipath IO request is cancelled (from
nvme_cancel_request()) we re-queue the bio innvme_failover_req(). Similarly, for non-multipath request, we do retry request innvme_retry_req()until retries for a request are maxed out bynvme_max_retries. So wouldn't it be appropriate to drop the cancelled request instead of retrying?
Quoted 8 lines
Quoted 2 lines
However, I do understand retrying a request on a different path when we got the request completion status specifying the path related error.
A cancelled request just means the host thinks the target failed to produce a response. It doesn't mean the host stopped caring about the command; the host still wants it to succeed, but determined corrective action is needed to reclaim and resubmit the command.
Thank Keith, got it!
--Nilay