blk-mq: improvement CPU hotplug
Subsystems (3)
v8 cover blk-mq: improvement CPU hotplug
Hi,
Thomas mentioned:
"
That was the constraint of managed interrupts from the very beginning:
The driver/subsystem has to quiesce the interrupt line and the associated queue _before_ it gets shutdown in CPU unplug and not fiddle with it until it's restarted by the core when the CPU is plugged in again.
"
But no drivers or blk-mq do that before one hctx becomes inactive(all CPUs for one hctx are offline), and even it is worse, blk-mq stills tries to run hw queue after hctx is dead, see blk_mq_hctx_notify_dead().
This patchset tries to address the issue by two stages:
1) add one new cpuhp state of CPUHP_AP_BLK_MQ_ONLINE
- mark the hctx as internal stopped, and drain all in-flight requests if the hctx is going to be dead.
2) re-submit IO in the state of CPUHP_BLK_MQ_DEAD after the hctx becomes dead
- steal bios from the request, and resubmit them via generic_make_request(), then these IO will be mapped to other live hctx for dispatch
Thanks John Garry for running lots of tests on arm64 with this patchset and co-working on investigating all kinds of issues.
Thanks Christoph's review on V7.
Please comment & review, thanks!
https://github.com/ming1/linux/commits/v5.7-rc-blk-mq-improve-cpu-hotplug
V8:
- add patches to share code with blk_rq_prep_clone
- code re-organization as suggested by Christoph, most of them are in 04/11, 10/11
- add reviewed-by tag
V7:
- fix updating .nr_active in get_driver_tag
- add hctx->cpumask check in cpuhp handler
- only drain requests which tag is >= 0
- pass more aggressive cpuhotplug&io test
V6:
- simplify getting driver tag, so that we can drain in-flight requests correctly without using synchronize_rcu()
- handle re-submission of flush & passthrough request correctly
V5:
- rename BLK_MQ_S_INTERNAL_STOPPED as BLK_MQ_S_INACTIVE
- re-factor code for re-submit requests in cpu dead hotplug handler
- address requeue corner case
V4:
- resubmit IOs in dispatch list in case that this hctx is dead
V3:
- re-organize patch 2 & 3 a bit for addressing Hannes's comment
- fix patch 4 for avoiding potential deadlock, as found by Hannes
V2:
- patch4 & patch 5 in V1 have been merged to block tree, so remove them
- address comments from John Garry and Minwoo
Ming Lei (11):
block: clone nr_integrity_segments and write_hint in blk_rq_prep_clone
block: add helper for copying request
blk-mq: mark blk_mq_get_driver_tag as static
blk-mq: assign rq->tag in blk_mq_get_driver_tag
blk-mq: support rq filter callback when iterating rqs
blk-mq: prepare for draining IO when hctx's all CPUs are offline
blk-mq: stop to handle IO and drain IO before hctx becomes inactive
block: add blk_end_flush_machinery
blk-mq: add blk_mq_hctx_handle_dead_cpu for handling cpu dead
blk-mq: re-submit IO in case that hctx is inactive
block: deactivate hctx when the hctx is actually inactive
block/blk-core.c | 29 +-- block/blk-flush.c | 141 ++++++++++++--- block/blk-mq-debugfs.c | 2 + block/blk-mq-tag.c | 39 ++-- block/blk-mq-tag.h | 4 + block/blk-mq.c | 353 +++++++++++++++++++++++++++++-------- block/blk-mq.h | 22 ++- block/blk.h | 11 +- drivers/block/loop.c | 2 +- drivers/md/dm-rq.c | 2 +- include/linux/blk-mq.h | 6 + include/linux/cpuhotplug.h | 1 + 12 files changed, 479 insertions(+), 133 deletions(-)
Signature · 1 line
2.25.2
PATCH v8 1/11 block: clone nr_integrity_segments and write_hint in blk_rq_prep_clone
So far blk_rq_prep_clone() is only used for setup one underlying cloned request from dm-rq request. block intetrity can be enabled for both dm-rq and the underlying queues, so it is reasonable to clone rq's nr_integrity_segments. Also write_hint is from bio, it should have been cloned too.
So clone nr_integrity_segments and write_hint in blk_rq_prep_clone.
--- block/blk-core.c | 4 ++++ 1 file changed, 4 insertions(+)
block/blk-core.c +4 -0
@@ -1636,9 +1636,13 @@ int blk_rq_prep_clone(struct request *rq, struct request *rq_src, rq->rq_flags |=RQF_SPECIAL_PAYLOAD ; rq->special_vec = rq_src->special_vec; } +#ifdef CONFIG_BLK_DEV_INTEGRITY + rq->nr_integrity_segments = rq_src->nr_integrity_segments; +#endif rq->nr_phys_segments = rq_src->nr_phys_segments; rq->ioprio = rq_src->ioprio; rq->extra_len = rq_src->extra_len; + rq->write_hint = rq_src->write_hint;return 0 ;
Signature · 1 line
2.25.2
Re: [PATCH V8 01/11] block: clone nr_integrity_segments and write_hint in blk_rq_prep_clone
Quoted 7 lines · Ming Lei
So far
blk_rq_prep_clone()is only used for setup one underlying cloned request from dm-rq request. block intetrity can be enabled for both dm-rq and the underlying queues, so it is reasonable to clone rq'snr_integrity_segments. Alsowrite_hintis from bio, it should have been cloned too.So clone
nr_integrity_segmentsandwrite_hintinblk_rq_prep_clone.
Looks good,
Re: [PATCH V8 01/11] block: clone nr_integrity_segments and write_hint in blk_rq_prep_clone
In reply to Ming LeiQuoted 29 lines · Ming Lei
So far
blk_rq_prep_clone()is only used for setup one underlying cloned request from dm-rq request. block intetrity can be enabled for both dm-rq and the underlying queues, so it is reasonable to clone rq'snr_integrity_segments. Alsowrite_hintis from bio, it should have been cloned too.So clone
nr_integrity_segmentsandwrite_hintinblk_rq_prep_clone.Cc John Garry <[email protected]>Cc Bart Van Assche <[email protected]>Cc Hannes Reinecke <[email protected]>Cc Christoph Hellwig <[email protected]>Cc Thomas Gleixner <[email protected]>Cc Mike Snitzer <[email protected]>Signed-off-by Ming Lei <[email protected]>--- block/blk-core.c | 4 ++++ 1 file changed, 4 insertions(+)block/blk-core.c +0
-0@@ -1636,9 +1636,13 @@ int blk_rq_prep_clone(struct request *rq, struct request *rq_src, rq->rq_flags |=RQF_SPECIAL_PAYLOAD ; rq->special_vec = rq_src->special_vec; }
block/blk-core.c int blk_rq_prep_clone(struct request *rq, struct request *rq_src, · line 1648
Quoted 10 lines
block/blk-core.c +4
-0+#ifdef CONFIG_BLK_DEV_INTEGRITY + rq->nr_integrity_segments = rq_src->nr_integrity_segments; +#endif rq->nr_phys_segments = rq_src->nr_phys_segments; rq->ioprio = rq_src->ioprio; rq->extra_len = rq_src->extra_len; + rq->write_hint = rq_src->write_hint;return 0 ;
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke Teamlead Storage & Networking [email protected] +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
Re: [PATCH V8 01/11] block: clone nr_integrity_segments and write_hint in blk_rq_prep_clone
In reply to Ming LeiMing,
Quoted 5 lines
So far
blk_rq_prep_clone()is only used for setup one underlying cloned request from dm-rq request. block intetrity can be enabled for both dm-rq and the underlying queues, so it is reasonable to clone rq'snr_integrity_segments. Alsowrite_hintis from bio, it should have been cloned too.
Signature · 1 line
Martin K. Petersen Oracle Linux Engineering
PATCH v8 2/11 block: add helper for copying request
In reply to Ming LeiAdd one new helper of blk_rq_copy_request() to copy request, and the helper will be used in this patch for re-submitting request, so make it as a block layer internal helper.
--- block/blk-core.c | 33 +++++++++++++++++++-------------- block/blk.h | 2 ++ 2 files changed, 21 insertions(+), 14 deletions(-)
block/blk-core.c +19 -14
@@ -1587,6 +1587,24 @@ void blk_rq_unprep_clone(struct request *rq) }EXPORT_SYMBOL_GPL (blk_rq_unprep_clone); +void blk_rq_copy_request (struct request *rq,struct request *rq_src) +{ +/* Copy attributes of the original request to the clone request. */ + rq->__sector =blk_rq_pos (rq_src); + rq->__data_len =blk_rq_bytes (rq_src); +if (rq_src->rq_flags &RQF_SPECIAL_PAYLOAD ) { + rq->rq_flags |=RQF_SPECIAL_PAYLOAD ; + rq->special_vec = rq_src->special_vec; + } +#ifdef CONFIG_BLK_DEV_INTEGRITY + rq->nr_integrity_segments = rq_src->nr_integrity_segments; +#endif + rq->nr_phys_segments = rq_src->nr_phys_segments; + rq->ioprio = rq_src->ioprio; + rq->extra_len = rq_src->extra_len; + rq->write_hint = rq_src->write_hint; +} +/** * blk_rq_prep_clone - Helper function to setup clone request * @rq: the request to be setup
@@ -1629,20 +1647,7 @@ int blk_rq_prep_clone(struct request *rq, struct request *rq_src, rq->bio = rq->biotail = bio; } -/* Copy attributes of the original request to the clone request. */ - rq->__sector =blk_rq_pos (rq_src); - rq->__data_len =blk_rq_bytes (rq_src); -if (rq_src->rq_flags &RQF_SPECIAL_PAYLOAD ) { - rq->rq_flags |=RQF_SPECIAL_PAYLOAD ; - rq->special_vec = rq_src->special_vec; - } -#ifdef CONFIG_BLK_DEV_INTEGRITY - rq->nr_integrity_segments = rq_src->nr_integrity_segments; -#endif - rq->nr_phys_segments = rq_src->nr_phys_segments; - rq->ioprio = rq_src->ioprio; - rq->extra_len = rq_src->extra_len; - rq->write_hint = rq_src->write_hint; +blk_rq_copy_request (rq, rq_src);return 0 ;
block/blk.h +2 -0
@@ -120,6 +120,8 @@ static inline void blk_rq_bio_prep(struct request *rq, struct bio *bio, rq->rq_disk = bio->bi_disk; } +void blk_rq_copy_request (struct request *rq,struct request *rq_src); +#ifdef CONFIG_BLK_DEV_INTEGRITY void blk_flush_integrity (void );bool __bio_integrity_endio (struct bio *);
Signature · 1 line
2.25.2
Re: [PATCH V8 02/11] block: add helper for copying request
Quoted 3 lines · Ming Lei
Add one new helper of
blk_rq_copy_request()to copy request, and the helper will be used in this patch for re-submitting request, so make it as a block layer internal helper.
Looks good,
Re: [PATCH V8 02/11] block: add helper for copying request
In reply to Ming LeiQuoted 12 lines · Ming Lei
Add one new helper of
blk_rq_copy_request()to copy request, and the helper will be used in this patch for re-submitting request, so make it as a block layer internal helper.Cc John Garry <[email protected]>Cc Bart Van Assche <[email protected]>Cc Hannes Reinecke <[email protected]>Cc Christoph Hellwig <[email protected]>Cc Thomas Gleixner <[email protected]>Cc Mike Snitzer <[email protected]>Signed-off-by Ming Lei <[email protected]>
Quoted 5 lines
--- block/blk-core.c | 33 +++++++++++++++++++-------------- block/blk.h | 2 ++ 2 files changed, 21 insertions(+), 14 deletions(-)Reviewed-by Hannes Reinecke <[email protected]>
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke Teamlead Storage & Networking [email protected] +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
Re: [PATCH V8 02/11] block: add helper for copying request
In reply to Ming LeiMing,
Quoted 3 lines
Add one new helper of
blk_rq_copy_request()to copy request, and the helper will be used in this patch for re-submitting request, so make it as a block layer internal helper.
Signature · 1 line
Martin K. Petersen Oracle Linux Engineering
PATCH v8 3/11 blk-mq: mark blk_mq_get_driver_tag as static
In reply to Ming LeiNow all callers of blk_mq_get_driver_tag are in blk-mq.c, so mark it as static.
--- block/blk-mq.c | 2 +- block/blk-mq.h | 1 - 2 files changed, 1 insertion(+), 2 deletions(-)
block/blk-mq.c +1 -1
@@ -1027,7 +1027,7 @@ static inline unsigned int queued_to_index(unsigned int queued)return min (BLK_MQ_MAX_DISPATCH_ORDER -1 ,ilog2 (queued) +1 ); } -bool blk_mq_get_driver_tag (struct request *rq) +static bool blk_mq_get_driver_tag (struct request *rq) {struct blk_mq_alloc_data data = { .q = rq->q,
block/blk-mq.h +0 -1
@@ -44,7 +44,6 @@ bool blk_mq_dispatch_rq_list(struct request_queue *, struct list_head *, bool);void blk_mq_add_to_requeue_list (struct request *rq,bool at_head,bool kick_requeue_list);void blk_mq_flush_busy_ctxs (struct blk_mq_hw_ctx *hctx,struct list_head *list); -bool blk_mq_get_driver_tag (struct request *rq);struct request *blk_mq_dequeue_from_ctx (struct blk_mq_hw_ctx *hctx,struct blk_mq_ctx *start);
Signature · 1 line
2.25.2
Re: [PATCH V8 03/11] blk-mq: mark blk_mq_get_driver_tag as static
Quoted 34 lines · Ming Lei
Now all callers of
blk_mq_get_driver_tagare inblk-mq.c, so mark it as static.Cc Bart Van Assche <[email protected]>Cc Hannes Reinecke <[email protected]>Cc Christoph Hellwig <[email protected]>Cc Thomas Gleixner <[email protected]>Cc John Garry <[email protected]>Reviewed-by Christoph Hellwig <[email protected]>Signed-off-by Ming Lei <[email protected]>--- block/blk-mq.c | 2 +- block/blk-mq.h | 1 - 2 files changed, 1 insertion(+), 2 deletions(-)block/blk-mq.c +1
-1@@ -1027,7 +1027,7 @@ static inline unsigned int queued_to_index(unsigned int queued)return min (BLK_MQ_MAX_DISPATCH_ORDER -1 ,ilog2 (queued) +1 ); } -bool blk_mq_get_driver_tag (struct request *rq) +static bool blk_mq_get_driver_tag (struct request *rq) {struct blk_mq_alloc_data data = { .q = rq->q,block/blk-mq.h +0
-0
block/blk-mq.h bool blk_mq_dispatch_rq_list(struct request_queue *, struct list_head *, bool); · line 49
Quoted 7 lines
block/blk-mq.h +0
-1@@ -44,7 +44,6 @@ bool blk_mq_dispatch_rq_list(struct request_queue *, struct list_head *, bool);void blk_mq_add_to_requeue_list (struct request *rq,bool at_head,bool kick_requeue_list);void blk_mq_flush_busy_ctxs (struct blk_mq_hw_ctx *hctx,struct list_head *list); -bool blk_mq_get_driver_tag (struct request *rq);struct request *blk_mq_dequeue_from_ctx (struct blk_mq_hw_ctx *hctx,struct blk_mq_ctx *start);
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke Teamlead Storage & Networking [email protected] +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
Re: [PATCH V8 03/11] blk-mq: mark blk_mq_get_driver_tag as static
In reply to Ming LeiMing,
Quoted 2 lines
Now all callers of
blk_mq_get_driver_tagare inblk-mq.c, so mark it as static.
Signature · 1 line
Martin K. Petersen Oracle Linux Engineering
PATCH v8 4/11 blk-mq: assign rq->tag in blk_mq_get_driver_tag
In reply to Ming LeiEspecially for none elevator, rq->tag is assigned after the request is allocated, so there isn't any way to figure out if one request is in being dispatched. Also the code path wrt. driver tag becomes a bit difference between none and io scheduler.
When one hctx becomes inactive, we have to prevent any request from being dispatched to LLD. And get driver tag provides one perfect chance to do that. Meantime we can drain any such requests by checking if rq->tag is assigned.
So only assign rq->tag until blk_mq_get_driver_tag() is called.
This way also simplifies code of dealing with driver tag a lot.
--- block/blk-flush.c | 18 ++---------- block/blk-mq.c | 75 ++++++++++++++++++++++++----------------------- block/blk-mq.h | 21 +++++++------ block/blk.h | 5 ---- 4 files changed, 51 insertions(+), 68 deletions(-)
block/blk-flush.c +3 -15
@@ -236,13 +236,8 @@ static void flush_end_io(struct request *flush_rq, blk_status_t error) error = fq->rq_status; hctx = flush_rq->mq_hctx; -if (!q->elevator) { -blk_mq_tag_set_rq (hctx, flush_rq->tag, fq->orig_rq); - flush_rq->tag =-1 ; - }else { -blk_mq_put_driver_tag (flush_rq); - flush_rq->internal_tag =-1 ; - } + flush_rq->internal_tag =-1 ; +blk_mq_put_driver_tag (flush_rq); running = &fq->flush_queue[fq->flush_running_idx];BUG_ON (fq->flush_pending_idx == fq->flush_running_idx);
@@ -317,14 +312,7 @@ static void blk_kick_flush(struct request_queue *q, struct blk_flush_queue *fq, flush_rq->mq_ctx = first_rq->mq_ctx; flush_rq->mq_hctx = first_rq->mq_hctx; -if (!q->elevator) { - fq->orig_rq = first_rq; - flush_rq->tag = first_rq->tag; -blk_mq_tag_set_rq (flush_rq->mq_hctx, first_rq->tag, flush_rq); - }else { - flush_rq->internal_tag = first_rq->internal_tag; - } - + flush_rq->internal_tag = first_rq->internal_tag; flush_rq->cmd_flags =REQ_OP_FLUSH |REQ_PREFLUSH ; flush_rq->cmd_flags |= (flags &REQ_DRV ) | (flags &REQ_FAILFAST_MASK ); flush_rq->rq_flags |=RQF_FLUSH_SEQ ;
block/blk-mq.c +38 -37
110 lines not on this page · raw message
block/blk-mq.h +10 -11
@@ -196,26 +196,25 @@ static inline bool blk_mq_get_dispatch_budget(struct blk_mq_hw_ctx *hctx)return true; } -static inline void __blk_mq_put_driver_tag (struct blk_mq_hw_ctx *hctx, -struct request *rq) +static inline void blk_mq_put_driver_tag (struct request *rq) { -blk_mq_put_tag (hctx->tags, rq->mq_ctx, rq->tag); +struct blk_mq_hw_ctx *hctx = rq->mq_hctx; +int tag = rq->tag; + +if (tag <0 ) +return ; + rq->tag =-1 ; +if (hctx->sched_tags) +blk_mq_put_tag (hctx->tags, rq->mq_ctx, tag); +if (rq->rq_flags &RQF_MQ_INFLIGHT ) { rq->rq_flags &= ~RQF_MQ_INFLIGHT ;atomic_dec (&hctx->nr_active); } } -static inline void blk_mq_put_driver_tag (struct request *rq) -{ -if (rq->tag ==-1 || rq->internal_tag ==-1 ) -return ; - -__blk_mq_put_driver_tag (rq->mq_hctx, rq); -} -static inline void blk_mq_clear_mq_map (struct blk_mq_queue_map *qmap) {int cpu;
block/blk.h +0 -5
@@ -26,11 +26,6 @@ struct blk_flush_queue {struct list_head flush_data_in_flight;struct request *flush_rq; -/* -* flush_rq shares tag with this rq, both can't be active -* at the same time -*/ -struct request *orig_rq;struct lock_class_key key;spinlock_t mq_flush_lock; };
Signature · 1 line
2.25.2
Re: [PATCH V8 04/11] blk-mq: assign rq->tag in blk_mq_get_driver_tag
Quoted 5 lines · Ming Lei
Especially for none elevator,
rq->tagis assigned after the request is allocated, so there isn't any way to figure out if one request is in being dispatched. Also the code path wrt. driver tag becomes a bit difference between none and io scheduler.
Quoted 8 lines
When one hctx becomes inactive, we have to prevent any request from being dispatched to LLD. And get driver tag provides one perfect chance to do that. Meantime we can drain any such requests by checking if
rq->tagis assigned.So only assign
rq->taguntilblk_mq_get_driver_tag()is called.This way also simplifies code of dealing with driver tag a lot.
Looks good,
Re: [PATCH V8 04/11] blk-mq: assign rq->tag in blk_mq_get_driver_tag
In reply to Ming LeiQuoted 10 lines · Ming Lei
Especially for none elevator,
rq->tagis assigned after the request is allocated, so there isn't any way to figure out if one request is in being dispatched. Also the code path wrt. driver tag becomes a bit difference between none and io scheduler.When one hctx becomes inactive, we have to prevent any request from being dispatched to LLD. And get driver tag provides one perfect chance to do that. Meantime we can drain any such requests by checking if
rq->tagis assigned.
Sorry for being a bit dense, but I'm having a hard time following the description. Maybe this would be a bit clearer:
When one hctx becomes inactive, we do have to prevent any request from
being dispatched to the LLD. If we intercept them in blk_mq_get_tag() we can also drain all those requests which have no rq->tag assigned.
(With the nice side effect that if above paragraph is correct I've also got it right what the patch is trying to do :-)
Quoted 103 lines
So only assign
rq->taguntilblk_mq_get_driver_tag()is called.This way also simplifies code of dealing with driver tag a lot.
Cc Bart Van Assche <[email protected]>Cc Hannes Reinecke <[email protected]>Cc Christoph Hellwig <[email protected]>Cc Thomas Gleixner <[email protected]>Cc John Garry <[email protected]>Signed-off-by Ming Lei <[email protected]>--- block/blk-flush.c | 18 ++---------- block/blk-mq.c | 75 ++++++++++++++++++++++++----------------------- block/blk-mq.h | 21 +++++++------ block/blk.h | 5 ---- 4 files changed, 51 insertions(+), 68 deletions(-)block/blk-flush.c +3
-15@@ -236,13 +236,8 @@ static void flush_end_io(struct request *flush_rq, blk_status_t error) error = fq->rq_status; hctx = flush_rq->mq_hctx; -if (!q->elevator) { -blk_mq_tag_set_rq (hctx, flush_rq->tag, fq->orig_rq); - flush_rq->tag =-1 ; - }else { -blk_mq_put_driver_tag (flush_rq); - flush_rq->internal_tag =-1 ; - } + flush_rq->internal_tag =-1 ; +blk_mq_put_driver_tag (flush_rq); running = &fq->flush_queue[fq->flush_running_idx];BUG_ON (fq->flush_pending_idx == fq->flush_running_idx);@@ -317,14 +312,7 @@ static void blk_kick_flush(struct request_queue *q, struct blk_flush_queue *fq, flush_rq->mq_ctx = first_rq->mq_ctx; flush_rq->mq_hctx = first_rq->mq_hctx; -if (!q->elevator) { - fq->orig_rq = first_rq; - flush_rq->tag = first_rq->tag; -blk_mq_tag_set_rq (flush_rq->mq_hctx, first_rq->tag, flush_rq); - }else { - flush_rq->internal_tag = first_rq->internal_tag; - } - + flush_rq->internal_tag = first_rq->internal_tag; flush_rq->cmd_flags =REQ_OP_FLUSH |REQ_PREFLUSH ; flush_rq->cmd_flags |= (flags &REQ_DRV ) | (flags &REQ_FAILFAST_MASK ); flush_rq->rq_flags |=RQF_FLUSH_SEQ ;block/blk-mq.c +11
-17@@ -276,18 +276,8 @@ static struct request *blk_mq_rq_ctx_init(struct blk_mq_alloc_data *data,struct request *rq = tags->static_rqs[tag];req_flags_t rq_flags =0 ; -if (data->flags &BLK_MQ_REQ_INTERNAL ) { - rq->tag =-1 ; - rq->internal_tag = tag; - }else { -if (data->hctx->flags &BLK_MQ_F_TAG_SHARED ) { - rq_flags =RQF_MQ_INFLIGHT ; -atomic_inc (&data->hctx->nr_active); - } - rq->tag = tag; - rq->internal_tag =-1 ; - data->hctx->tags->rqs[rq->tag] = rq; - } + rq->internal_tag = tag; + rq->tag =-1 ;/* csd/requeue_work/fifo_time is initialized before use */ rq->q = data->q;@@ -472,14 +462,18 @@ static void __blk_mq_free_request(struct request *rq)struct request_queue *q = rq->q;struct blk_mq_ctx *ctx = rq->mq_ctx;struct blk_mq_hw_ctx *hctx = rq->mq_hctx; -const int sched_tag = rq->internal_tag;blk_pm_mark_last_busy (rq); rq->mq_hctx =NULL ; -if (rq->tag !=-1 ) -blk_mq_put_tag (hctx->tags, ctx, rq->tag); -if (sched_tag !=-1 ) -blk_mq_put_tag (hctx->sched_tags, ctx, sched_tag); + +if (hctx->sched_tags) { +if (rq->tag >=0 ) +blk_mq_put_tag (hctx->tags, ctx, rq->tag); +blk_mq_put_tag (hctx->sched_tags, ctx, rq->internal_tag); + }else { +blk_mq_put_tag (hctx->tags, ctx, rq->internal_tag); + } +blk_mq_sched_restart (hctx);blk_queue_exit (q); }
block/blk-mq.c inline void __blk_mq_end_request(struct request *rq, blk_status_t error) · line 527
Quoted 8 lines
block/blk-mq.c +1
-1@@ -527,7 +521,7 @@ inline void __blk_mq_end_request(struct request *rq, blk_status_t error)blk_stat_add (rq, now); } -if (rq->internal_tag !=-1 ) +if (rq->q->elevator && rq->internal_tag !=-1 )blk_mq_sched_completed_request (rq, now);blk_account_io_done (rq, now);
One really does wonder: under which circumstances can 'internal_tag' be -1 now ?
The hunk above seems to imply that 'internal_tag' is now always be set; and this is also the impression I got from reading this patch. Care to elaborate?
Quoted 73 lines
block/blk-mq.c +26
-19@@ -1027,33 +1021,40 @@ static inline unsigned int queued_to_index(unsigned int queued)return min (BLK_MQ_MAX_DISPATCH_ORDER -1 ,ilog2 (queued) +1 ); } -static bool blk_mq_get_driver_tag (struct request *rq) +static bool __blk_mq_get_driver_tag (struct request *rq) {struct blk_mq_alloc_data data = { - .q = rq->q, - .hctx = rq->mq_hctx, - .flags =BLK_MQ_REQ_NOWAIT , - .cmd_flags = rq->cmd_flags, + .q = rq->q, + .hctx = rq->mq_hctx, + .flags =BLK_MQ_REQ_NOWAIT , + .cmd_flags = rq->cmd_flags, }; -bool shared; -if (rq->tag !=-1 ) -return true; +if (data.hctx->sched_tags) { +if (blk_mq_tag_is_reserved (data.hctx->sched_tags, + rq->internal_tag)) + data.flags |=BLK_MQ_REQ_RESERVED ; + rq->tag =blk_mq_get_tag (&data); + }else { + rq->tag = rq->internal_tag; + } -if (blk_mq_tag_is_reserved (data.hctx->sched_tags, rq->internal_tag)) - data.flags |=BLK_MQ_REQ_RESERVED ; +if (rq->tag ==-1 ) +return false; - shared =blk_mq_tag_busy (data.hctx); - rq->tag =blk_mq_get_tag (&data); -if (rq->tag >=0 ) { -if (shared) { - rq->rq_flags |=RQF_MQ_INFLIGHT ; -atomic_inc (&data.hctx->nr_active); - } - data.hctx->tags->rqs[rq->tag] = rq; +if (blk_mq_tag_busy (data.hctx)) { + rq->rq_flags |=RQF_MQ_INFLIGHT ; +atomic_inc (&data.hctx->nr_active); } + data.hctx->tags->rqs[rq->tag] = rq; +return true; +} -return rq->tag !=-1 ; +static bool blk_mq_get_driver_tag (struct request *rq) +{ +if (rq->tag !=-1 ) +return true; +return __blk_mq_get_driver_tag (rq); } static int blk_mq_dispatch_wake(wait_queue_entry_t *wait, unsigned mode,block/blk-mq.h +1
-3@@ -196,26 +196,25 @@ static inline bool blk_mq_get_dispatch_budget(struct blk_mq_hw_ctx *hctx)return true; } -static inline void __blk_mq_put_driver_tag (struct blk_mq_hw_ctx *hctx, -struct request *rq) +static inline void blk_mq_put_driver_tag (struct request *rq) { -blk_mq_put_tag (hctx->tags, rq->mq_ctx, rq->tag);
block/blk-mq.h static inline bool blk_mq_get_dispatch_budget(struct blk_mq_hw_ctx *hctx) · line 210
Quoted 10 lines
block/blk-mq.h +8
-0+struct blk_mq_hw_ctx *hctx = rq->mq_hctx; +int tag = rq->tag; + +if (tag <0 ) +return ; + rq->tag =-1 ; > + if (hctx->sched_tags) +blk_mq_put_tag (hctx->tags, rq->mq_ctx, tag); +
I wonder if you need the local variable 'tag' here; might it not be better to set 'rq->tag' to '-1' after the call to put_tag?
But then I'm not sure, either, so it might just be cosmetic ..
Quoted 24 lines
block/blk-mq.h +0
-8if (rq->rq_flags &RQF_MQ_INFLIGHT ) { rq->rq_flags &= ~RQF_MQ_INFLIGHT ;atomic_dec (&hctx->nr_active); } } -static inline void blk_mq_put_driver_tag (struct request *rq) -{ -if (rq->tag ==-1 || rq->internal_tag ==-1 ) -return ; - -__blk_mq_put_driver_tag (rq->mq_hctx, rq); -} -static inline void blk_mq_clear_mq_map (struct blk_mq_queue_map *qmap) {int cpu;block/blk.h +0
-0@@ -26,11 +26,6 @@ struct blk_flush_queue {struct list_head flush_data_in_flight;
block/blk.h struct blk_flush_queue { · line 31
Quoted 10 lines
block/blk.h +0
-5struct request *flush_rq; -/* -* flush_rq shares tag with this rq, both can't be active -* at the same time -*/ -struct request *orig_rq;struct lock_class_key key;spinlock_t mq_flush_lock; };
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke Teamlead Storage & Networking [email protected] +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
Re: [PATCH V8 04/11] blk-mq: assign rq->tag in blk_mq_get_driver_tag
Quoted 12 lines · Hannes Reinecke
Quoted 10 lines · Ming Lei
Especially for none elevator,
rq->tagis assigned after the request is allocated, so there isn't any way to figure out if one request is in being dispatched. Also the code path wrt. driver tag becomes a bit difference between none and io scheduler.When one hctx becomes inactive, we have to prevent any request from being dispatched to LLD. And get driver tag provides one perfect chance to do that. Meantime we can drain any such requests by checking if
rq->tagis assigned.
Quoted 7 lines
Sorry for being a bit dense, but I'm having a hard time following the description.
Maybe this would be a bit clearer:When one hctx becomes inactive, we do have to prevent any request from being dispatched to the LLD. If we intercept them in
blk_mq_get_tag()we can also drain all those requests which have norq->tagassigned.
No, actually what we need to drain is requests with rq->tag assigned, and if tag isn't assigned, we can simply prevent the request from being queued to LLD after the hctx becomes inactive.
Frankly speaking, the description in commit log should be more clear, and correct.
Quoted 105 lines
(With the nice side effect that if above paragraph is correct I've also got it right what the patch is trying to do :-)
Quoted 101 lines
So only assign
rq->taguntilblk_mq_get_driver_tag()is called.This way also simplifies code of dealing with driver tag a lot.
Cc Bart Van Assche <[email protected]>Cc Hannes Reinecke <[email protected]>Cc Christoph Hellwig <[email protected]>Cc Thomas Gleixner <[email protected]>Cc John Garry <[email protected]>Signed-off-by Ming Lei <[email protected]>--- block/blk-flush.c | 18 ++---------- block/blk-mq.c | 75 ++++++++++++++++++++++++----------------------- block/blk-mq.h | 21 +++++++------ block/blk.h | 5 ---- 4 files changed, 51 insertions(+), 68 deletions(-)block/blk-flush.c +3
-15@@ -236,13 +236,8 @@ static void flush_end_io(struct request *flush_rq, blk_status_t error) error = fq->rq_status; hctx = flush_rq->mq_hctx; -if (!q->elevator) { -blk_mq_tag_set_rq (hctx, flush_rq->tag, fq->orig_rq); - flush_rq->tag =-1 ; - }else { -blk_mq_put_driver_tag (flush_rq); - flush_rq->internal_tag =-1 ; - } + flush_rq->internal_tag =-1 ; +blk_mq_put_driver_tag (flush_rq); running = &fq->flush_queue[fq->flush_running_idx];BUG_ON (fq->flush_pending_idx == fq->flush_running_idx);@@ -317,14 +312,7 @@ static void blk_kick_flush(struct request_queue *q, struct blk_flush_queue *fq, flush_rq->mq_ctx = first_rq->mq_ctx; flush_rq->mq_hctx = first_rq->mq_hctx; -if (!q->elevator) { - fq->orig_rq = first_rq; - flush_rq->tag = first_rq->tag; -blk_mq_tag_set_rq (flush_rq->mq_hctx, first_rq->tag, flush_rq); - }else { - flush_rq->internal_tag = first_rq->internal_tag; - } - + flush_rq->internal_tag = first_rq->internal_tag; flush_rq->cmd_flags =REQ_OP_FLUSH |REQ_PREFLUSH ; flush_rq->cmd_flags |= (flags &REQ_DRV ) | (flags &REQ_FAILFAST_MASK ); flush_rq->rq_flags |=RQF_FLUSH_SEQ ;block/blk-mq.c +12
-18@@ -276,18 +276,8 @@ static struct request *blk_mq_rq_ctx_init(struct blk_mq_alloc_data *data,struct request *rq = tags->static_rqs[tag];req_flags_t rq_flags =0 ; -if (data->flags &BLK_MQ_REQ_INTERNAL ) { - rq->tag =-1 ; - rq->internal_tag = tag; - }else { -if (data->hctx->flags &BLK_MQ_F_TAG_SHARED ) { - rq_flags =RQF_MQ_INFLIGHT ; -atomic_inc (&data->hctx->nr_active); - } - rq->tag = tag; - rq->internal_tag =-1 ; - data->hctx->tags->rqs[rq->tag] = rq; - } + rq->internal_tag = tag; + rq->tag =-1 ;/* csd/requeue_work/fifo_time is initialized before use */ rq->q = data->q;@@ -472,14 +462,18 @@ static void __blk_mq_free_request(struct request *rq)struct request_queue *q = rq->q;struct blk_mq_ctx *ctx = rq->mq_ctx;struct blk_mq_hw_ctx *hctx = rq->mq_hctx; -const int sched_tag = rq->internal_tag;blk_pm_mark_last_busy (rq); rq->mq_hctx =NULL ; -if (rq->tag !=-1 ) -blk_mq_put_tag (hctx->tags, ctx, rq->tag); -if (sched_tag !=-1 ) -blk_mq_put_tag (hctx->sched_tags, ctx, sched_tag); + +if (hctx->sched_tags) { +if (rq->tag >=0 ) +blk_mq_put_tag (hctx->tags, ctx, rq->tag); +blk_mq_put_tag (hctx->sched_tags, ctx, rq->internal_tag); + }else { +blk_mq_put_tag (hctx->tags, ctx, rq->internal_tag); + } +blk_mq_sched_restart (hctx);blk_queue_exit (q); }@@ -527,7 +521,7 @@ inline void __blk_mq_end_request(struct request *rq, blk_status_t error)blk_stat_add (rq, now); } -if (rq->internal_tag !=-1 ) +if (rq->q->elevator && rq->internal_tag !=-1 )
Quoted 8 lines
block/blk-mq.c inline void __blk_mq_end_request(struct request *rq, blk_status_t error) · line 527
Quoted 2 lines
block/blk-mq.c +0
-0blk_mq_sched_completed_request (rq, now);blk_account_io_done (rq, now);One really does wonder: under which circumstances can '
internal_tag' be -1 now ?
The hunk above seems to imply that 'internal_tag' is now always be set; and this is also the impression I got from reading this patch.
Care to elaborate?
rq->internal_tag should always be assigned, and the only case is that it can become -1 for flush rq, however it is done in .end_io(), so we may avoid the above check on rq->internal_tag.
Quoted 71 lines
Quoted 71 lines
block/blk-mq.c +26
-19@@ -1027,33 +1021,40 @@ static inline unsigned int queued_to_index(unsigned int queued)return min (BLK_MQ_MAX_DISPATCH_ORDER -1 ,ilog2 (queued) +1 ); } -static bool blk_mq_get_driver_tag (struct request *rq) +static bool __blk_mq_get_driver_tag (struct request *rq) {struct blk_mq_alloc_data data = { - .q = rq->q, - .hctx = rq->mq_hctx, - .flags =BLK_MQ_REQ_NOWAIT , - .cmd_flags = rq->cmd_flags, + .q = rq->q, + .hctx = rq->mq_hctx, + .flags =BLK_MQ_REQ_NOWAIT , + .cmd_flags = rq->cmd_flags, }; -bool shared; -if (rq->tag !=-1 ) -return true; +if (data.hctx->sched_tags) { +if (blk_mq_tag_is_reserved (data.hctx->sched_tags, + rq->internal_tag)) + data.flags |=BLK_MQ_REQ_RESERVED ; + rq->tag =blk_mq_get_tag (&data); + }else { + rq->tag = rq->internal_tag; + } -if (blk_mq_tag_is_reserved (data.hctx->sched_tags, rq->internal_tag)) - data.flags |=BLK_MQ_REQ_RESERVED ; +if (rq->tag ==-1 ) +return false; - shared =blk_mq_tag_busy (data.hctx); - rq->tag =blk_mq_get_tag (&data); -if (rq->tag >=0 ) { -if (shared) { - rq->rq_flags |=RQF_MQ_INFLIGHT ; -atomic_inc (&data.hctx->nr_active); - } - data.hctx->tags->rqs[rq->tag] = rq; +if (blk_mq_tag_busy (data.hctx)) { + rq->rq_flags |=RQF_MQ_INFLIGHT ; +atomic_inc (&data.hctx->nr_active); } + data.hctx->tags->rqs[rq->tag] = rq; +return true; +} -return rq->tag !=-1 ; +static bool blk_mq_get_driver_tag (struct request *rq) +{ +if (rq->tag !=-1 ) +return true; +return __blk_mq_get_driver_tag (rq); } static int blk_mq_dispatch_wake(wait_queue_entry_t *wait, unsigned mode,block/blk-mq.h +5
-3@@ -196,26 +196,25 @@ static inline bool blk_mq_get_dispatch_budget(struct blk_mq_hw_ctx *hctx)return true; } -static inline void __blk_mq_put_driver_tag (struct blk_mq_hw_ctx *hctx, -struct request *rq) +static inline void blk_mq_put_driver_tag (struct request *rq) { -blk_mq_put_tag (hctx->tags, rq->mq_ctx, rq->tag); +struct blk_mq_hw_ctx *hctx = rq->mq_hctx; +int tag = rq->tag; + +if (tag <0 )
Quoted 8 lines
block/blk-mq.h static inline bool blk_mq_get_dispatch_budget(struct blk_mq_hw_ctx *hctx) · line 211
Quoted 6 lines
block/blk-mq.h +4
-0+return ; + rq->tag =-1 ; > + if (hctx->sched_tags) +blk_mq_put_tag (hctx->tags, rq->mq_ctx, tag); +I wonder if you need the local variable 'tag' here; might it not be better to set '
rq->tag' to '-1' after the call toput_tag?
No, we can't touch the request after blk_mq_put_tag() returns.
I remember we have fixed such kind of UAF several times.
Thanks,
Ming
Hannes Reinecke
Reviewed-byRe: [PATCH V8 04/11] blk-mq: assign rq->tag in blk_mq_get_driver_tag
Quoted 21 lines · Ming Lei
Quoted 12 lines · Hannes Reinecke
Quoted 10 lines · Ming Lei
Especially for none elevator,
rq->tagis assigned after the request is allocated, so there isn't any way to figure out if one request is in being dispatched. Also the code path wrt. driver tag becomes a bit difference between none and io scheduler.When one hctx becomes inactive, we have to prevent any request from being dispatched to LLD. And get driver tag provides one perfect chance to do that. Meantime we can drain any such requests by checking if
rq->tagis assigned.Quoted 7 lines
Sorry for being a bit dense, but I'm having a hard time following the description.
Maybe this would be a bit clearer:When one hctx becomes inactive, we do have to prevent any request from being dispatched to the LLD. If we intercept them in
blk_mq_get_tag()we can also drain all those requests which have norq->tagassigned.
Quoted 7 lines
No, actually what we need to drain is requests with
rq->tagassigned, and if tag isn't assigned, we can simply prevent the request from being queued to LLD after the hctx becomes inactive.Frankly speaking, the description in commit log should be more clear, and correct.
Ah. Thanks for the explanation.
Quoted 114 lines
Quoted 105 lines
(With the nice side effect that if above paragraph is correct I've also got it right what the patch is trying to do :-)
Quoted 101 lines
So only assign
rq->taguntilblk_mq_get_driver_tag()is called.This way also simplifies code of dealing with driver tag a lot.
Cc Bart Van Assche <[email protected]>Cc Hannes Reinecke <[email protected]>Cc Christoph Hellwig <[email protected]>Cc Thomas Gleixner <[email protected]>Cc John Garry <[email protected]>Signed-off-by Ming Lei <[email protected]>--- block/blk-flush.c | 18 ++---------- block/blk-mq.c | 75 ++++++++++++++++++++++++----------------------- block/blk-mq.h | 21 +++++++------ block/blk.h | 5 ---- 4 files changed, 51 insertions(+), 68 deletions(-)block/blk-flush.c +3
-15@@ -236,13 +236,8 @@ static void flush_end_io(struct request *flush_rq, blk_status_t error) error = fq->rq_status; hctx = flush_rq->mq_hctx; -if (!q->elevator) { -blk_mq_tag_set_rq (hctx, flush_rq->tag, fq->orig_rq); - flush_rq->tag =-1 ; - }else { -blk_mq_put_driver_tag (flush_rq); - flush_rq->internal_tag =-1 ; - } + flush_rq->internal_tag =-1 ; +blk_mq_put_driver_tag (flush_rq); running = &fq->flush_queue[fq->flush_running_idx];BUG_ON (fq->flush_pending_idx == fq->flush_running_idx);@@ -317,14 +312,7 @@ static void blk_kick_flush(struct request_queue *q, struct blk_flush_queue *fq, flush_rq->mq_ctx = first_rq->mq_ctx; flush_rq->mq_hctx = first_rq->mq_hctx; -if (!q->elevator) { - fq->orig_rq = first_rq; - flush_rq->tag = first_rq->tag; -blk_mq_tag_set_rq (flush_rq->mq_hctx, first_rq->tag, flush_rq); - }else { - flush_rq->internal_tag = first_rq->internal_tag; - } - + flush_rq->internal_tag = first_rq->internal_tag; flush_rq->cmd_flags =REQ_OP_FLUSH |REQ_PREFLUSH ; flush_rq->cmd_flags |= (flags &REQ_DRV ) | (flags &REQ_FAILFAST_MASK ); flush_rq->rq_flags |=RQF_FLUSH_SEQ ;block/blk-mq.c +12
-18@@ -276,18 +276,8 @@ static struct request *blk_mq_rq_ctx_init(struct blk_mq_alloc_data *data,struct request *rq = tags->static_rqs[tag];req_flags_t rq_flags =0 ; -if (data->flags &BLK_MQ_REQ_INTERNAL ) { - rq->tag =-1 ; - rq->internal_tag = tag; - }else { -if (data->hctx->flags &BLK_MQ_F_TAG_SHARED ) { - rq_flags =RQF_MQ_INFLIGHT ; -atomic_inc (&data->hctx->nr_active); - } - rq->tag = tag; - rq->internal_tag =-1 ; - data->hctx->tags->rqs[rq->tag] = rq; - } + rq->internal_tag = tag; + rq->tag =-1 ;/* csd/requeue_work/fifo_time is initialized before use */ rq->q = data->q;@@ -472,14 +462,18 @@ static void __blk_mq_free_request(struct request *rq)struct request_queue *q = rq->q;struct blk_mq_ctx *ctx = rq->mq_ctx;struct blk_mq_hw_ctx *hctx = rq->mq_hctx; -const int sched_tag = rq->internal_tag;blk_pm_mark_last_busy (rq); rq->mq_hctx =NULL ; -if (rq->tag !=-1 ) -blk_mq_put_tag (hctx->tags, ctx, rq->tag); -if (sched_tag !=-1 ) -blk_mq_put_tag (hctx->sched_tags, ctx, sched_tag); + +if (hctx->sched_tags) { +if (rq->tag >=0 ) +blk_mq_put_tag (hctx->tags, ctx, rq->tag); +blk_mq_put_tag (hctx->sched_tags, ctx, rq->internal_tag); + }else { +blk_mq_put_tag (hctx->tags, ctx, rq->internal_tag); + } +blk_mq_sched_restart (hctx);blk_queue_exit (q); }@@ -527,7 +521,7 @@ inline void __blk_mq_end_request(struct request *rq, blk_status_t error)blk_stat_add (rq, now); } -if (rq->internal_tag !=-1 ) +if (rq->q->elevator && rq->internal_tag !=-1 )Quoted 8 lines
block/blk-mq.c inline void __blk_mq_end_request(struct request *rq, blk_status_t error) · line 527
Quoted 2 lines
block/blk-mq.c +0
-0blk_mq_sched_completed_request (rq, now);blk_account_io_done (rq, now);One really does wonder: under which circumstances can '
internal_tag' be -1 now ?
The hunk above seems to imply that 'internal_tag' is now always be set; and this is also the impression I got from reading this patch.
Care to elaborate?
Quoted 4 lines
rq->internal_tagshould always be assigned, and the only case is that it can become -1 for flush rq, however it is done in .end_io(), so we may avoid the above check onrq->internal_tag.
Thought so.
Quoted 80 lines
Quoted 71 lines
Quoted 71 lines
block/blk-mq.c +26
-19@@ -1027,33 +1021,40 @@ static inline unsigned int queued_to_index(unsigned int queued)return min (BLK_MQ_MAX_DISPATCH_ORDER -1 ,ilog2 (queued) +1 ); } -static bool blk_mq_get_driver_tag (struct request *rq) +static bool __blk_mq_get_driver_tag (struct request *rq) {struct blk_mq_alloc_data data = { - .q = rq->q, - .hctx = rq->mq_hctx, - .flags =BLK_MQ_REQ_NOWAIT , - .cmd_flags = rq->cmd_flags, + .q = rq->q, + .hctx = rq->mq_hctx, + .flags =BLK_MQ_REQ_NOWAIT , + .cmd_flags = rq->cmd_flags, }; -bool shared; -if (rq->tag !=-1 ) -return true; +if (data.hctx->sched_tags) { +if (blk_mq_tag_is_reserved (data.hctx->sched_tags, + rq->internal_tag)) + data.flags |=BLK_MQ_REQ_RESERVED ; + rq->tag =blk_mq_get_tag (&data); + }else { + rq->tag = rq->internal_tag; + } -if (blk_mq_tag_is_reserved (data.hctx->sched_tags, rq->internal_tag)) - data.flags |=BLK_MQ_REQ_RESERVED ; +if (rq->tag ==-1 ) +return false; - shared =blk_mq_tag_busy (data.hctx); - rq->tag =blk_mq_get_tag (&data); -if (rq->tag >=0 ) { -if (shared) { - rq->rq_flags |=RQF_MQ_INFLIGHT ; -atomic_inc (&data.hctx->nr_active); - } - data.hctx->tags->rqs[rq->tag] = rq; +if (blk_mq_tag_busy (data.hctx)) { + rq->rq_flags |=RQF_MQ_INFLIGHT ; +atomic_inc (&data.hctx->nr_active); } + data.hctx->tags->rqs[rq->tag] = rq; +return true; +} -return rq->tag !=-1 ; +static bool blk_mq_get_driver_tag (struct request *rq) +{ +if (rq->tag !=-1 ) +return true; +return __blk_mq_get_driver_tag (rq); } static int blk_mq_dispatch_wake(wait_queue_entry_t *wait, unsigned mode,block/blk-mq.h +5
-3@@ -196,26 +196,25 @@ static inline bool blk_mq_get_dispatch_budget(struct blk_mq_hw_ctx *hctx)return true; } -static inline void __blk_mq_put_driver_tag (struct blk_mq_hw_ctx *hctx, -struct request *rq) +static inline void blk_mq_put_driver_tag (struct request *rq) { -blk_mq_put_tag (hctx->tags, rq->mq_ctx, rq->tag); +struct blk_mq_hw_ctx *hctx = rq->mq_hctx; +int tag = rq->tag; + +if (tag <0 )Quoted 8 lines
block/blk-mq.h static inline bool blk_mq_get_dispatch_budget(struct blk_mq_hw_ctx *hctx) · line 211
Quoted 6 lines
block/blk-mq.h +4
-0+return ; + rq->tag =-1 ; > + if (hctx->sched_tags) +blk_mq_put_tag (hctx->tags, rq->mq_ctx, tag); +I wonder if you need the local variable 'tag' here; might it not be better to set '
rq->tag' to '-1' after the call toput_tag?
Quoted 4 lines
No, we can't touch the request after
blk_mq_put_tag()returns.I remember we have fixed such kind of UAF several times.
Ah, right, of course.
FWIW:
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke Teamlead Storage & Networking [email protected] +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
PATCH v8 5/11 blk-mq: support rq filter callback when iterating rqs
In reply to Ming LeiNow request is thought as in-flight only when its state is updated as MQ_RQ_IN_FLIGHT, which is done by dirver via blk_mq_start_request().
Actually from blk-mq's view, one rq can be thought as in-flight after its tag is >= 0.
Passing one rq filter callback so that we can iterating requests very flexiable.
Meantime blk_mq_all_tag_busy_iter is defined as public, which will be called from blk-mq internally.
--- block/blk-mq-tag.c | 39 +++++++++++++++++++++++++++------------ block/blk-mq-tag.h | 4 ++++ 2 files changed, 31 insertions(+), 12 deletions(-)
block/blk-mq-tag.c +27 -12
@@ -255,6 +255,7 @@ static void bt_for_each(struct blk_mq_hw_ctx *hctx, struct sbitmap_queue *bt,struct bt_tags_iter_data {struct blk_mq_tags *tags;busy_tag_iter_fn *fn; +busy_rq_iter_fn *busy_rq_fn;void *data;bool reserved; };
@@ -274,7 +275,7 @@ static bool bt_tags_iter(struct sbitmap *bitmap, unsigned int bitnr, void *data)* test and set the bit before assining ->rqs[]. */ rq = tags->rqs[bitnr]; -if (rq &&blk_mq_request_started (rq)) +if (rq && iter_data->busy_rq_fn (rq, iter_data->data, reserved))return iter_data->fn (rq, iter_data->data, reserved);return true;
@@ -294,11 +295,13 @@ static bool bt_tags_iter(struct sbitmap *bitmap, unsigned int bitnr, void *data)* bitmap_tags member of struct blk_mq_tags. */ static void bt_tags_for_each (struct blk_mq_tags *tags,struct sbitmap_queue *bt, -busy_tag_iter_fn *fn,void *data,bool reserved) +busy_tag_iter_fn *fn,busy_rq_iter_fn *busy_rq_fn, +void *data,bool reserved) {struct bt_tags_iter_data iter_data = { .tags = tags, .fn = fn, + .busy_rq_fn = busy_rq_fn, .data = data, .reserved = reserved, };
@@ -310,19 +313,30 @@ static void bt_tags_for_each(struct blk_mq_tags *tags, struct sbitmap_queue *bt,/** * blk_mq_all_tag_busy_iter - iterate over all started requests in a tag map * @tags: Tag map to iterate over. -* @fn: Pointer to the function that will be called for each started -* request. @fn will be called as follows: @fn(rq, @priv, -* reserved) where rq is a pointer to a request. 'reserved' -* indicates whether or not @rq is a reserved request. Return -* true to continue iterating tags, false to stop. +* @fn: Pointer to the function that will be called for each request +* when .busy_rq_fn(rq) returns true. @fn will be called as +* follows: @fn(rq, @priv, reserved) where rq is a pointer to a +* request. 'reserved' indicates whether or not @rq is a reserved +* request. Return true to continue iterating tags, false to stop. +* @busy_rq_fn: Pointer to the function that will be called for each request, +* @busy_rq_fn's type is same with @fn. Only when @busy_rq_fn(rq, +* @priv, reserved) returns true, @fn will be called on this rq. * @priv: Will be passed as second argument to @fn. */ -static void blk_mq_all_tag_busy_iter (struct blk_mq_tags *tags, -busy_tag_iter_fn *fn,void *priv) +void blk_mq_all_tag_busy_iter (struct blk_mq_tags *tags, +busy_tag_iter_fn *fn,busy_rq_iter_fn *busy_rq_fn, +void *priv) {if (tags->nr_reserved_tags) -bt_tags_for_each (tags, &tags->breserved_tags, fn, priv, true); -bt_tags_for_each (tags, &tags->bitmap_tags, fn, priv, false); +bt_tags_for_each (tags, &tags->breserved_tags, fn, busy_rq_fn, + priv, true); +bt_tags_for_each (tags, &tags->bitmap_tags, fn, busy_rq_fn, priv, false); +} + +static bool blk_mq_default_busy_rq (struct request *rq,void *data, +bool reserved) +{ +return blk_mq_request_started (rq); }/**
@@ -342,7 +356,8 @@ void blk_mq_tagset_busy_iter(struct blk_mq_tag_set *tagset,for (i =0 ; i < tagset->nr_hw_queues; i++) {if (tagset->tags && tagset->tags[i]) -blk_mq_all_tag_busy_iter (tagset->tags[i], fn, priv); +blk_mq_all_tag_busy_iter (tagset->tags[i], fn, + blk_mq_default_busy_rq, priv); } }EXPORT_SYMBOL (blk_mq_tagset_busy_iter);
block/blk-mq-tag.h +4 -0
@@ -21,6 +21,7 @@ struct blk_mq_tags {struct list_head page_list; }; +typedef bool (busy_rq_iter_fn )(struct request *,void *,bool );extern struct blk_mq_tags *blk_mq_init_tags (unsigned int nr_tags,unsigned int reserved_tags,int node,int alloc_policy);extern void blk_mq_free_tags (struct blk_mq_tags *tags);
@@ -34,6 +35,9 @@ extern int blk_mq_tag_update_depth(struct blk_mq_hw_ctx *hctx,extern void blk_mq_tag_wakeup_all (struct blk_mq_tags *tags,bool );void blk_mq_queue_tag_busy_iter (struct request_queue *q,busy_iter_fn *fn,void *priv); +void blk_mq_all_tag_busy_iter (struct blk_mq_tags *tags, +busy_tag_iter_fn *fn,busy_rq_iter_fn *busy_rq_fn, +void *priv);static inline struct sbq_wait_state *bt_wait_ptr (struct sbitmap_queue *bt,struct blk_mq_hw_ctx *hctx)
Signature · 1 line
2.25.2
Re: [PATCH V8 05/11] blk-mq: support rq filter callback when iterating rqs
Quoted 3 lines · Ming Lei
Now request is thought as in-flight only when its state is updated as
MQ_RQ_IN_FLIGHT, which is done by dirver viablk_mq_start_request().
driver
Quoted 3 lines
Actually from blk-mq's view, one rq can be thought as in-flight after its tag is >= 0.
Well, and that we should clarify to avoid any misunderstanding. To my understanding, 'in-flight' are request which are submitted to the LLD. IE we'll have a lifetime rule like
internal_tag >= tag > in-flight
If the existence of a 'tag' would be equivalent to 'in-flight' we could do away with all the convoluted code managing the MQ_RQ_IN_FLIGHT state, wouldn't we?
Quoted 3 lines
Passing one rq filter callback so that we can iterating requests very flexiable.
flexible
Quoted 3 lines
Meantime
blk_mq_all_tag_busy_iteris defined as public, which will be called from blk-mq internally.
Maybe:
Implement blk_mq_all_tag_busy_iter() which accepts a 'busy_fn' argument
to filter over which commands to iterate, and make the existing blk_mq_tag_busy_iter() a wrapper for the new function.
Quoted 112 lines
Cc John Garry <[email protected]>Cc Bart Van Assche <[email protected]>Cc Hannes Reinecke <[email protected]>Cc Christoph Hellwig <[email protected]>Cc Thomas Gleixner <[email protected]>Reviewed-by Christoph Hellwig <[email protected]>Signed-off-by Ming Lei <[email protected]>--- block/blk-mq-tag.c | 39 +++++++++++++++++++++++++++------------ block/blk-mq-tag.h | 4 ++++ 2 files changed, 31 insertions(+), 12 deletions(-)block/blk-mq-tag.c +27
-12@@ -255,6 +255,7 @@ static void bt_for_each(struct blk_mq_hw_ctx *hctx, struct sbitmap_queue *bt,struct bt_tags_iter_data {struct blk_mq_tags *tags;busy_tag_iter_fn *fn; +busy_rq_iter_fn *busy_rq_fn;void *data;bool reserved; };@@ -274,7 +275,7 @@ static bool bt_tags_iter(struct sbitmap *bitmap, unsigned int bitnr, void *data)* test and set the bit before assining ->rqs[]. */ rq = tags->rqs[bitnr]; -if (rq &&blk_mq_request_started (rq)) +if (rq && iter_data->busy_rq_fn (rq, iter_data->data, reserved))return iter_data->fn (rq, iter_data->data, reserved);return true;@@ -294,11 +295,13 @@ static bool bt_tags_iter(struct sbitmap *bitmap, unsigned int bitnr, void *data)* bitmap_tags member of struct blk_mq_tags. */ static void bt_tags_for_each (struct blk_mq_tags *tags,struct sbitmap_queue *bt, -busy_tag_iter_fn *fn,void *data,bool reserved) +busy_tag_iter_fn *fn,busy_rq_iter_fn *busy_rq_fn, +void *data,bool reserved) {struct bt_tags_iter_data iter_data = { .tags = tags, .fn = fn, + .busy_rq_fn = busy_rq_fn, .data = data, .reserved = reserved, };@@ -310,19 +313,30 @@ static void bt_tags_for_each(struct blk_mq_tags *tags, struct sbitmap_queue *bt,/** * blk_mq_all_tag_busy_iter - iterate over all started requests in a tag map * @tags: Tag map to iterate over. -* @fn: Pointer to the function that will be called for each started -* request. @fn will be called as follows: @fn(rq, @priv, -* reserved) where rq is a pointer to a request. 'reserved' -* indicates whether or not @rq is a reserved request. Return -* true to continue iterating tags, false to stop. +* @fn: Pointer to the function that will be called for each request +* when .busy_rq_fn(rq) returns true. @fn will be called as +* follows: @fn(rq, @priv, reserved) where rq is a pointer to a +* request. 'reserved' indicates whether or not @rq is a reserved +* request. Return true to continue iterating tags, false to stop. +* @busy_rq_fn: Pointer to the function that will be called for each request, +* @busy_rq_fn's type is same with @fn. Only when @busy_rq_fn(rq, +* @priv, reserved) returns true, @fn will be called on this rq. * @priv: Will be passed as second argument to @fn. */ -static void blk_mq_all_tag_busy_iter (struct blk_mq_tags *tags, -busy_tag_iter_fn *fn,void *priv) +void blk_mq_all_tag_busy_iter (struct blk_mq_tags *tags, +busy_tag_iter_fn *fn,busy_rq_iter_fn *busy_rq_fn, +void *priv) {if (tags->nr_reserved_tags) -bt_tags_for_each (tags, &tags->breserved_tags, fn, priv, true); -bt_tags_for_each (tags, &tags->bitmap_tags, fn, priv, false); +bt_tags_for_each (tags, &tags->breserved_tags, fn, busy_rq_fn, + priv, true); +bt_tags_for_each (tags, &tags->bitmap_tags, fn, busy_rq_fn, priv, false); +} + +static bool blk_mq_default_busy_rq (struct request *rq,void *data, +bool reserved) +{ +return blk_mq_request_started (rq); }/** @@ -342,7 +356,8 @@ void blk_mq_tagset_busy_iter(struct blk_mq_tag_set *tagset,for (i =0 ; i < tagset->nr_hw_queues; i++) {if (tagset->tags && tagset->tags[i]) -blk_mq_all_tag_busy_iter (tagset->tags[i], fn, priv); +blk_mq_all_tag_busy_iter (tagset->tags[i], fn, + blk_mq_default_busy_rq, priv); } }EXPORT_SYMBOL (blk_mq_tagset_busy_iter);block/blk-mq-tag.h +1
-0@@ -21,6 +21,7 @@ struct blk_mq_tags {struct list_head page_list; }; +typedef bool (busy_rq_iter_fn )(struct request *,void *,bool );extern struct blk_mq_tags *blk_mq_init_tags (unsigned int nr_tags,unsigned int reserved_tags,int node,int alloc_policy);extern void blk_mq_free_tags (struct blk_mq_tags *tags);
block/blk-mq-tag.h extern int blk_mq_tag_update_depth(struct blk_mq_hw_ctx *hctx, · line 43
Quoted 9 lines
block/blk-mq-tag.h +3
-0@@ -34,6 +35,9 @@ extern int blk_mq_tag_update_depth(struct blk_mq_hw_ctx *hctx,extern void blk_mq_tag_wakeup_all (struct blk_mq_tags *tags,bool );void blk_mq_queue_tag_busy_iter (struct request_queue *q,busy_iter_fn *fn,void *priv); +void blk_mq_all_tag_busy_iter (struct blk_mq_tags *tags, +busy_tag_iter_fn *fn,busy_rq_iter_fn *busy_rq_fn, +void *priv);static inline struct sbq_wait_state *bt_wait_ptr (struct sbitmap_queue *bt,struct blk_mq_hw_ctx *hctx)
I do worry about the performance impact of this new filter function.
From my understanding, the _busy_iter() functions are supposed to be efficient, such that they can be used as an alternative to having a global atomic counter. (cf the replacement of the global host_busy counter).
But if we're adding ever more functionality to the iterator itself there's a good chance we'll kill the performance rendering this assumption invalid.
Have you measured the performance impact of this?
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke Teamlead Storage & Networking [email protected] +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
Re: [PATCH V8 05/11] blk-mq: support rq filter callback when iterating rqs
Quoted 14 lines · Hannes Reinecke
Quoted 3 lines · Ming Lei
Now request is thought as in-flight only when its state is updated as
MQ_RQ_IN_FLIGHT, which is done by dirver viablk_mq_start_request().driver
Quoted 3 lines
Actually from blk-mq's view, one rq can be thought as in-flight after its tag is >= 0.
Well, and that we should clarify to avoid any misunderstanding. To my understanding, 'in-flight' are request which are submitted to the LLD. IE we'll have a lifetime rule like
Quoted 5 lines
internal_tag>= tag > in-flightIf the existence of a 'tag' would be equivalent to 'in-flight' we could do away with all the convoluted code managing the
MQ_RQ_IN_FLIGHTstate, wouldn't we?
Yeah, I have been thinking about that.
Quoted 7 lines
Quoted 4 lines
Passing one rq filter callback so that we can iterating requests very flexiable.
flexible
Quoted 8 lines
Quoted 3 lines
Meantime
blk_mq_all_tag_busy_iteris defined as public, which will be called from blk-mq internally.Maybe:
Implement
blk_mq_all_tag_busy_iter()which accepts a 'busy_fn' argument to filter over which commands to iterate, and make the existingblk_mq_tag_busy_iter()a wrapper for the new function.
Fine.
Quoted 111 lines
Quoted 111 lines
Cc John Garry <[email protected]>Cc Bart Van Assche <[email protected]>Cc Hannes Reinecke <[email protected]>Cc Christoph Hellwig <[email protected]>Cc Thomas Gleixner <[email protected]>Reviewed-by Christoph Hellwig <[email protected]>Signed-off-by Ming Lei <[email protected]>--- block/blk-mq-tag.c | 39 +++++++++++++++++++++++++++------------ block/blk-mq-tag.h | 4 ++++ 2 files changed, 31 insertions(+), 12 deletions(-)block/blk-mq-tag.c +27
-12@@ -255,6 +255,7 @@ static void bt_for_each(struct blk_mq_hw_ctx *hctx, struct sbitmap_queue *bt,struct bt_tags_iter_data {struct blk_mq_tags *tags;busy_tag_iter_fn *fn; +busy_rq_iter_fn *busy_rq_fn;void *data;bool reserved; };@@ -274,7 +275,7 @@ static bool bt_tags_iter(struct sbitmap *bitmap, unsigned int bitnr, void *data)* test and set the bit before assining ->rqs[]. */ rq = tags->rqs[bitnr]; -if (rq &&blk_mq_request_started (rq)) +if (rq && iter_data->busy_rq_fn (rq, iter_data->data, reserved))return iter_data->fn (rq, iter_data->data, reserved);return true;@@ -294,11 +295,13 @@ static bool bt_tags_iter(struct sbitmap *bitmap, unsigned int bitnr, void *data)* bitmap_tags member of struct blk_mq_tags. */ static void bt_tags_for_each (struct blk_mq_tags *tags,struct sbitmap_queue *bt, -busy_tag_iter_fn *fn,void *data,bool reserved) +busy_tag_iter_fn *fn,busy_rq_iter_fn *busy_rq_fn, +void *data,bool reserved) {struct bt_tags_iter_data iter_data = { .tags = tags, .fn = fn, + .busy_rq_fn = busy_rq_fn, .data = data, .reserved = reserved, };@@ -310,19 +313,30 @@ static void bt_tags_for_each(struct blk_mq_tags *tags, struct sbitmap_queue *bt,/** * blk_mq_all_tag_busy_iter - iterate over all started requests in a tag map * @tags: Tag map to iterate over. -* @fn: Pointer to the function that will be called for each started -* request. @fn will be called as follows: @fn(rq, @priv, -* reserved) where rq is a pointer to a request. 'reserved' -* indicates whether or not @rq is a reserved request. Return -* true to continue iterating tags, false to stop. +* @fn: Pointer to the function that will be called for each request +* when .busy_rq_fn(rq) returns true. @fn will be called as +* follows: @fn(rq, @priv, reserved) where rq is a pointer to a +* request. 'reserved' indicates whether or not @rq is a reserved +* request. Return true to continue iterating tags, false to stop. +* @busy_rq_fn: Pointer to the function that will be called for each request, +* @busy_rq_fn's type is same with @fn. Only when @busy_rq_fn(rq, +* @priv, reserved) returns true, @fn will be called on this rq. * @priv: Will be passed as second argument to @fn. */ -static void blk_mq_all_tag_busy_iter (struct blk_mq_tags *tags, -busy_tag_iter_fn *fn,void *priv) +void blk_mq_all_tag_busy_iter (struct blk_mq_tags *tags, +busy_tag_iter_fn *fn,busy_rq_iter_fn *busy_rq_fn, +void *priv) {if (tags->nr_reserved_tags) -bt_tags_for_each (tags, &tags->breserved_tags, fn, priv, true); -bt_tags_for_each (tags, &tags->bitmap_tags, fn, priv, false); +bt_tags_for_each (tags, &tags->breserved_tags, fn, busy_rq_fn, + priv, true); +bt_tags_for_each (tags, &tags->bitmap_tags, fn, busy_rq_fn, priv, false); +} + +static bool blk_mq_default_busy_rq (struct request *rq,void *data, +bool reserved) +{ +return blk_mq_request_started (rq); }/** @@ -342,7 +356,8 @@ void blk_mq_tagset_busy_iter(struct blk_mq_tag_set *tagset,for (i =0 ; i < tagset->nr_hw_queues; i++) {if (tagset->tags && tagset->tags[i]) -blk_mq_all_tag_busy_iter (tagset->tags[i], fn, priv); +blk_mq_all_tag_busy_iter (tagset->tags[i], fn, + blk_mq_default_busy_rq, priv); } }EXPORT_SYMBOL (blk_mq_tagset_busy_iter);block/blk-mq-tag.h +2
-0@@ -21,6 +21,7 @@ struct blk_mq_tags {struct list_head page_list; }; +typedef bool (busy_rq_iter_fn )(struct request *,void *,bool );extern struct blk_mq_tags *blk_mq_init_tags (unsigned int nr_tags,unsigned int reserved_tags,int node,int alloc_policy);extern void blk_mq_free_tags (struct blk_mq_tags *tags);@@ -34,6 +35,9 @@ extern int blk_mq_tag_update_depth(struct blk_mq_hw_ctx *hctx,extern void blk_mq_tag_wakeup_all (struct blk_mq_tags *tags,bool );void blk_mq_queue_tag_busy_iter (struct request_queue *q,busy_iter_fn *fn,void *priv); +void blk_mq_all_tag_busy_iter(struct blk_mq_tags *tags,
Quoted 8 lines
block/blk-mq-tag.h extern int blk_mq_tag_update_depth(struct blk_mq_hw_ctx *hctx,
Quoted 5 lines
block/blk-mq-tag.h +2
-0+ busy_tag_iter_fn *fn, busy_rq_iter_fn *busy_rq_fn, + void *priv);static inline struct sbq_wait_state *bt_wait_ptr (struct sbitmap_queue *bt,struct blk_mq_hw_ctx *hctx)I do worry about the performance impact of this new filter function. From my understanding, the
_busy_iter()functions are supposed to be efficient, such that they can be used as an alternative to having a global
No, blk_mq_tagset_busy_iter() won't be called in fast IO path, usually it is run in EH code path.
Also I don't see how big the performance impact can be given what the patch is doing is just to add blk_mq_default_busy_rq() to replace the check of blk_mq_request_started().
Quoted 7 lines
atomic counter.
(cf the replacement of the globalhost_busycounter).But if we're adding ever more functionality to the iterator itself there's a good chance we'll kill the performance rendering this assumption invalid.
Have you measured the performance impact of this?
As I mentioned, we don't call such busy_iter() in fast path. Or do you see such usage in fast path?
thanks,
Ming
PATCH v8 6/11 blk-mq: prepare for draining IO when hctx's all CPUs are offline
In reply to Ming LeiMost of blk-mq drivers depend on managed IRQ's auto-affinity to setup up queue mapping. Thomas mentioned the following point[1]:
"
That was the constraint of managed interrupts from the very beginning:
The driver/subsystem has to quiesce the interrupt line and the associated queue _before_ it gets shutdown in CPU unplug and not fiddle with it until it's restarted by the core when the CPU is plugged in again.
"
However, current blk-mq implementation doesn't quiesce hw queue before the last CPU in the hctx is shutdown. Even worse, CPUHP_BLK_MQ_DEAD is one cpuhp state handled after the CPU is down, so there isn't any chance to quiesce hctx for blk-mq wrt. CPU hotplug.
Add new cpuhp state of CPUHP_AP_BLK_MQ_ONLINE for blk-mq to stop queues and wait for completion of in-flight requests.
We will stop hw queue and wait for completion of in-flight requests when one hctx is becoming dead in the following patch. This way may cause dead-lock for some stacking blk-mq drivers, such as dm-rq and loop.
Add blk-mq flag of BLK_MQ_F_NO_MANAGED_IRQ and mark it for dm-rq and loop, so we needn't to wait for completion of in-flight requests from dm-rq & loop, then the potential dead-lock can be avoided.
[1] https://lore.kernel.org/linux-block/[email protected]/
--- block/blk-mq-debugfs.c | 1 + block/blk-mq.c | 19 +++++++++++++++++++ drivers/block/loop.c | 2 +- drivers/md/dm-rq.c | 2 +- include/linux/blk-mq.h | 3 +++ include/linux/cpuhotplug.h | 1 + 6 files changed, 26 insertions(+), 2 deletions(-)
block/blk-mq-debugfs.c +1 -0
@@ -239,6 +239,7 @@ static const char *const hctx_flag_name[] = {HCTX_FLAG_NAME (TAG_SHARED ),HCTX_FLAG_NAME (BLOCKING ),HCTX_FLAG_NAME (NO_SCHED ), + HCTX_FLAG_NAME(NO_MANAGED_IRQ), };#undef HCTX_FLAG_NAME
block/blk-mq.c +19 -0
@@ -2261,6 +2261,16 @@ int blk_mq_alloc_rqs(struct blk_mq_tag_set *set, struct blk_mq_tags *tags,return -ENOMEM ; } +static int blk_mq_hctx_notify_online (unsigned int cpu,struct hlist_node *node) +{ +return 0 ; +} + +static int blk_mq_hctx_notify_offline (unsigned int cpu,struct hlist_node *node) +{ +return 0 ; +} +/* * 'cpu' is going away. splice any existing rq_list entries from this * software queue to the hw queue dispatch list, and ensure that it
@@ -2297,6 +2307,9 @@ static int blk_mq_hctx_notify_dead(unsigned int cpu, struct hlist_node *node)static void blk_mq_remove_cpuhp (struct blk_mq_hw_ctx *hctx) { +if (!(hctx->flags &BLK_MQ_F_NO_MANAGED_IRQ )) +cpuhp_state_remove_instance_nocalls (CPUHP_AP_BLK_MQ_ONLINE , + &hctx->cpuhp_online);cpuhp_state_remove_instance_nocalls (CPUHP_BLK_MQ_DEAD , &hctx->cpuhp_dead); }
@@ -2356,6 +2369,9 @@ static int blk_mq_init_hctx(struct request_queue *q, { hctx->queue_num = hctx_idx; +if (!(hctx->flags &BLK_MQ_F_NO_MANAGED_IRQ )) +cpuhp_state_add_instance_nocalls (CPUHP_AP_BLK_MQ_ONLINE , + &hctx->cpuhp_online);cpuhp_state_add_instance_nocalls (CPUHP_BLK_MQ_DEAD , &hctx->cpuhp_dead); hctx->tags = set->tags[hctx_idx];
@@ -3610,6 +3626,9 @@ static int __init blk_mq_init(void) {cpuhp_setup_state_multi (CPUHP_BLK_MQ_DEAD ,"block/mq:dead" ,NULL , blk_mq_hctx_notify_dead); +cpuhp_setup_state_multi (CPUHP_AP_BLK_MQ_ONLINE ,"block/mq:online" , + blk_mq_hctx_notify_online, + blk_mq_hctx_notify_offline);return 0 ; }subsys_initcall (blk_mq_init);
drivers/block/loop.c +1 -1
@@ -2037,7 +2037,7 @@ static int loop_add(struct loop_device **l, int i) lo->tag_set.queue_depth =128 ; lo->tag_set.numa_node =NUMA_NO_NODE ; lo->tag_set.cmd_size =sizeof (struct loop_cmd ); - lo->tag_set.flags =BLK_MQ_F_SHOULD_MERGE ; + lo->tag_set.flags =BLK_MQ_F_SHOULD_MERGE |BLK_MQ_F_NO_MANAGED_IRQ ; lo->tag_set.driver_data = lo; err =blk_mq_alloc_tag_set (&lo->tag_set);
drivers/md/dm-rq.c +1 -1
@@ -547,7 +547,7 @@ int dm_mq_init_request_queue(struct mapped_device *md, struct dm_table *t) md->tag_set->ops = &dm_mq_ops; md->tag_set->queue_depth =dm_get_blk_mq_queue_depth (); md->tag_set->numa_node = md->numa_node_id; - md->tag_set->flags =BLK_MQ_F_SHOULD_MERGE ; + md->tag_set->flags =BLK_MQ_F_SHOULD_MERGE |BLK_MQ_F_NO_MANAGED_IRQ ; md->tag_set->nr_hw_queues =dm_get_blk_mq_nr_hw_queues (); md->tag_set->driver_data = md;
include/linux/blk-mq.h +3 -0
@@ -140,6 +140,8 @@ struct blk_mq_hw_ctx {*/ atomic_t nr_active; +/** @cpuhp_online: List to store request if CPU is going to die */ +struct hlist_node cpuhp_online;/** @cpuhp_dead: List to store request if some CPU die. */ struct hlist_node cpuhp_dead;/** @kobj: Kernel object for sysfs. */
@@ -391,6 +393,7 @@ struct blk_mq_ops {enum {BLK_MQ_F_SHOULD_MERGE =1 <<0 ,BLK_MQ_F_TAG_SHARED =1 <<1 , +BLK_MQ_F_NO_MANAGED_IRQ =1 <<2 ,BLK_MQ_F_BLOCKING =1 <<5 ,BLK_MQ_F_NO_SCHED =1 <<6 ,BLK_MQ_F_ALLOC_POLICY_START_BIT =8 ,
include/linux/cpuhotplug.h +1 -0
@@ -152,6 +152,7 @@ enum cpuhp_state {CPUHP_AP_SMPBOOT_THREADS ,CPUHP_AP_X86_VDSO_VMA_ONLINE ,CPUHP_AP_IRQ_AFFINITY_ONLINE , +CPUHP_AP_BLK_MQ_ONLINE ,CPUHP_AP_ARM_MVEBU_SYNC_CLOCKS ,CPUHP_AP_X86_INTEL_EPB_ONLINE , CPUHP_AP_PERF_ONLINE,
Signature · 1 line
2.25.2
Re: [PATCH V8 06/11] blk-mq: prepare for draining IO when hctx's all CPUs are offline
Quoted 161 lines · Ming Lei
Most of blk-mq drivers depend on managed IRQ's auto-affinity to setup up queue mapping. Thomas mentioned the following point[1]:
"
That was the constraint of managed interrupts from the very beginning:The driver/subsystem has to quiesce the interrupt line and the associated queue _before_ it gets shutdown in CPU unplug and not fiddle with it until it's restarted by the core when the CPU is plugged in again.
"However, current blk-mq implementation doesn't quiesce hw queue before the last CPU in the hctx is shutdown. Even worse,
CPUHP_BLK_MQ_DEADis one cpuhp state handled after the CPU is down, so there isn't any chance to quiesce hctx for blk-mq wrt. CPU hotplug.Add new cpuhp state of
CPUHP_AP_BLK_MQ_ONLINEfor blk-mq to stop queues and wait for completion of in-flight requests.We will stop hw queue and wait for completion of in-flight requests when one hctx is becoming dead in the following patch. This way may cause dead-lock for some stacking blk-mq drivers, such as dm-rq and loop.
Add blk-mq flag of
BLK_MQ_F_NO_MANAGED_IRQand mark it for dm-rq and loop, so we needn't to wait for completion of in-flight requests from dm-rq & loop, then the potential dead-lock can be avoided.[1] https://lore.kernel.org/linux-block/[email protected]/
Cc John Garry <[email protected]>Cc Bart Van Assche <[email protected]>Cc Hannes Reinecke <[email protected]>Cc Christoph Hellwig <[email protected]>Cc Thomas Gleixner <[email protected]>Signed-off-by Ming Lei <[email protected]>--- block/blk-mq-debugfs.c | 1 + block/blk-mq.c | 19 +++++++++++++++++++ drivers/block/loop.c | 2 +- drivers/md/dm-rq.c | 2 +- include/linux/blk-mq.h | 3 +++ include/linux/cpuhotplug.h | 1 + 6 files changed, 26 insertions(+), 2 deletions(-)block/blk-mq-debugfs.c +1
-0@@ -239,6 +239,7 @@ static const char *const hctx_flag_name[] = {HCTX_FLAG_NAME (TAG_SHARED ),HCTX_FLAG_NAME (BLOCKING ),HCTX_FLAG_NAME (NO_SCHED ), + HCTX_FLAG_NAME(NO_MANAGED_IRQ), };#undef HCTX_FLAG_NAMEblock/blk-mq.c +19
-0@@ -2261,6 +2261,16 @@ int blk_mq_alloc_rqs(struct blk_mq_tag_set *set, struct blk_mq_tags *tags,return -ENOMEM ; } +static int blk_mq_hctx_notify_online (unsigned int cpu,struct hlist_node *node) +{ +return 0 ; +} + +static int blk_mq_hctx_notify_offline (unsigned int cpu,struct hlist_node *node) +{ +return 0 ; +} +/* * 'cpu' is going away. splice any existing rq_list entries from this * software queue to the hw queue dispatch list, and ensure that it @@ -2297,6 +2307,9 @@ static int blk_mq_hctx_notify_dead(unsigned int cpu, struct hlist_node *node)static void blk_mq_remove_cpuhp (struct blk_mq_hw_ctx *hctx) { +if (!(hctx->flags &BLK_MQ_F_NO_MANAGED_IRQ )) +cpuhp_state_remove_instance_nocalls (CPUHP_AP_BLK_MQ_ONLINE , + &hctx->cpuhp_online);cpuhp_state_remove_instance_nocalls (CPUHP_BLK_MQ_DEAD , &hctx->cpuhp_dead); }@@ -2356,6 +2369,9 @@ static int blk_mq_init_hctx(struct request_queue *q, { hctx->queue_num = hctx_idx; +if (!(hctx->flags &BLK_MQ_F_NO_MANAGED_IRQ )) +cpuhp_state_add_instance_nocalls (CPUHP_AP_BLK_MQ_ONLINE , + &hctx->cpuhp_online);cpuhp_state_add_instance_nocalls (CPUHP_BLK_MQ_DEAD , &hctx->cpuhp_dead); hctx->tags = set->tags[hctx_idx];@@ -3610,6 +3626,9 @@ static int __init blk_mq_init(void) {cpuhp_setup_state_multi (CPUHP_BLK_MQ_DEAD ,"block/mq:dead" ,NULL , blk_mq_hctx_notify_dead); +cpuhp_setup_state_multi (CPUHP_AP_BLK_MQ_ONLINE ,"block/mq:online" , + blk_mq_hctx_notify_online, + blk_mq_hctx_notify_offline);return 0 ; }subsys_initcall (blk_mq_init);drivers/block/loop.c +1
-1@@ -2037,7 +2037,7 @@ static int loop_add(struct loop_device **l, int i) lo->tag_set.queue_depth =128 ; lo->tag_set.numa_node =NUMA_NO_NODE ; lo->tag_set.cmd_size =sizeof (struct loop_cmd ); - lo->tag_set.flags =BLK_MQ_F_SHOULD_MERGE ; + lo->tag_set.flags =BLK_MQ_F_SHOULD_MERGE |BLK_MQ_F_NO_MANAGED_IRQ ; lo->tag_set.driver_data = lo; err =blk_mq_alloc_tag_set (&lo->tag_set);drivers/md/dm-rq.c +1
-1@@ -547,7 +547,7 @@ int dm_mq_init_request_queue(struct mapped_device *md, struct dm_table *t) md->tag_set->ops = &dm_mq_ops; md->tag_set->queue_depth =dm_get_blk_mq_queue_depth (); md->tag_set->numa_node = md->numa_node_id; - md->tag_set->flags =BLK_MQ_F_SHOULD_MERGE ; + md->tag_set->flags =BLK_MQ_F_SHOULD_MERGE |BLK_MQ_F_NO_MANAGED_IRQ ; md->tag_set->nr_hw_queues =dm_get_blk_mq_nr_hw_queues (); md->tag_set->driver_data = md;include/linux/blk-mq.h +3
-0@@ -140,6 +140,8 @@ struct blk_mq_hw_ctx {*/ atomic_t nr_active; +/** @cpuhp_online: List to store request if CPU is going to die */ +struct hlist_node cpuhp_online;/** @cpuhp_dead: List to store request if some CPU die. */ struct hlist_node cpuhp_dead;/** @kobj: Kernel object for sysfs. */ @@ -391,6 +393,7 @@ struct blk_mq_ops {enum {BLK_MQ_F_SHOULD_MERGE =1 <<0 ,BLK_MQ_F_TAG_SHARED =1 <<1 , +BLK_MQ_F_NO_MANAGED_IRQ =1 <<2 ,BLK_MQ_F_BLOCKING =1 <<5 ,BLK_MQ_F_NO_SCHED =1 <<6 ,BLK_MQ_F_ALLOC_POLICY_START_BIT =8 ,include/linux/cpuhotplug.h +0
-0
include/linux/cpuhotplug.h enum cpuhp_state { · line 158
Quoted 7 lines
include/linux/cpuhotplug.h +1
-0@@ -152,6 +152,7 @@ enum cpuhp_state {CPUHP_AP_SMPBOOT_THREADS ,CPUHP_AP_X86_VDSO_VMA_ONLINE ,CPUHP_AP_IRQ_AFFINITY_ONLINE , +CPUHP_AP_BLK_MQ_ONLINE ,CPUHP_AP_ARM_MVEBU_SYNC_CLOCKS ,CPUHP_AP_X86_INTEL_EPB_ONLINE , CPUHP_AP_PERF_ONLINE,
Ho-hum.
I do agree for the loop and the CPUHP part (not that I'm qualified to just the latter, but anyway).
For the dm side I'm less certain.
Thing is, we rarely get hardware interrupts directly to the device-mapper device, but rather to the underlying hardware LLD. I even not quite sure what exactly the implications of managed interrupts with dm are; after all, we're using softirqs here, don't we?
So for DM I'd rather wait for the I/O on the underlying devices' hctx to become quiesce, and not kill them ourselves. Not sure if the device-mapper framework _can_ do this right now, though.
Mike?
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke Teamlead Storage & Networking [email protected] +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
Re: [PATCH V8 06/11] blk-mq: prepare for draining IO when hctx's all CPUs are offline
Quoted 171 lines · Hannes Reinecke
Quoted 153 lines · Ming Lei
Most of blk-mq drivers depend on managed IRQ's auto-affinity to setup up queue mapping. Thomas mentioned the following point[1]:
"
That was the constraint of managed interrupts from the very beginning:The driver/subsystem has to quiesce the interrupt line and the associated queue _before_ it gets shutdown in CPU unplug and not fiddle with it until it's restarted by the core when the CPU is plugged in again.
"However, current blk-mq implementation doesn't quiesce hw queue before the last CPU in the hctx is shutdown. Even worse,
CPUHP_BLK_MQ_DEADis one cpuhp state handled after the CPU is down, so there isn't any chance to quiesce hctx for blk-mq wrt. CPU hotplug.Add new cpuhp state of
CPUHP_AP_BLK_MQ_ONLINEfor blk-mq to stop queues and wait for completion of in-flight requests.We will stop hw queue and wait for completion of in-flight requests when one hctx is becoming dead in the following patch. This way may cause dead-lock for some stacking blk-mq drivers, such as dm-rq and loop.
Add blk-mq flag of
BLK_MQ_F_NO_MANAGED_IRQand mark it for dm-rq and loop, so we needn't to wait for completion of in-flight requests from dm-rq & loop, then the potential dead-lock can be avoided.[1] https://lore.kernel.org/linux-block/[email protected]/
Cc John Garry <[email protected]>Cc Bart Van Assche <[email protected]>Cc Hannes Reinecke <[email protected]>Cc Christoph Hellwig <[email protected]>Cc Thomas Gleixner <[email protected]>Signed-off-by Ming Lei <[email protected]>--- block/blk-mq-debugfs.c | 1 + block/blk-mq.c | 19 +++++++++++++++++++ drivers/block/loop.c | 2 +- drivers/md/dm-rq.c | 2 +- include/linux/blk-mq.h | 3 +++ include/linux/cpuhotplug.h | 1 + 6 files changed, 26 insertions(+), 2 deletions(-)block/blk-mq-debugfs.c +1
-0@@ -239,6 +239,7 @@ static const char *const hctx_flag_name[] = {HCTX_FLAG_NAME (TAG_SHARED ),HCTX_FLAG_NAME (BLOCKING ),HCTX_FLAG_NAME (NO_SCHED ), + HCTX_FLAG_NAME(NO_MANAGED_IRQ), };#undef HCTX_FLAG_NAMEblock/blk-mq.c +19
-0@@ -2261,6 +2261,16 @@ int blk_mq_alloc_rqs(struct blk_mq_tag_set *set, struct blk_mq_tags *tags,return -ENOMEM ; } +static int blk_mq_hctx_notify_online (unsigned int cpu,struct hlist_node *node) +{ +return 0 ; +} + +static int blk_mq_hctx_notify_offline (unsigned int cpu,struct hlist_node *node) +{ +return 0 ; +} +/* * 'cpu' is going away. splice any existing rq_list entries from this * software queue to the hw queue dispatch list, and ensure that it @@ -2297,6 +2307,9 @@ static int blk_mq_hctx_notify_dead(unsigned int cpu, struct hlist_node *node)static void blk_mq_remove_cpuhp (struct blk_mq_hw_ctx *hctx) { +if (!(hctx->flags &BLK_MQ_F_NO_MANAGED_IRQ )) +cpuhp_state_remove_instance_nocalls (CPUHP_AP_BLK_MQ_ONLINE , + &hctx->cpuhp_online);cpuhp_state_remove_instance_nocalls (CPUHP_BLK_MQ_DEAD , &hctx->cpuhp_dead); }@@ -2356,6 +2369,9 @@ static int blk_mq_init_hctx(struct request_queue *q, { hctx->queue_num = hctx_idx; +if (!(hctx->flags &BLK_MQ_F_NO_MANAGED_IRQ )) +cpuhp_state_add_instance_nocalls (CPUHP_AP_BLK_MQ_ONLINE , + &hctx->cpuhp_online);cpuhp_state_add_instance_nocalls (CPUHP_BLK_MQ_DEAD , &hctx->cpuhp_dead); hctx->tags = set->tags[hctx_idx];@@ -3610,6 +3626,9 @@ static int __init blk_mq_init(void) {cpuhp_setup_state_multi (CPUHP_BLK_MQ_DEAD ,"block/mq:dead" ,NULL , blk_mq_hctx_notify_dead); +cpuhp_setup_state_multi (CPUHP_AP_BLK_MQ_ONLINE ,"block/mq:online" , + blk_mq_hctx_notify_online, + blk_mq_hctx_notify_offline);return 0 ; }subsys_initcall (blk_mq_init);drivers/block/loop.c +1
-1@@ -2037,7 +2037,7 @@ static int loop_add(struct loop_device **l, int i) lo->tag_set.queue_depth =128 ; lo->tag_set.numa_node =NUMA_NO_NODE ; lo->tag_set.cmd_size =sizeof (struct loop_cmd ); - lo->tag_set.flags =BLK_MQ_F_SHOULD_MERGE ; + lo->tag_set.flags =BLK_MQ_F_SHOULD_MERGE |BLK_MQ_F_NO_MANAGED_IRQ ; lo->tag_set.driver_data = lo; err =blk_mq_alloc_tag_set (&lo->tag_set);drivers/md/dm-rq.c +1
-1@@ -547,7 +547,7 @@ int dm_mq_init_request_queue(struct mapped_device *md, struct dm_table *t) md->tag_set->ops = &dm_mq_ops; md->tag_set->queue_depth =dm_get_blk_mq_queue_depth (); md->tag_set->numa_node = md->numa_node_id; - md->tag_set->flags =BLK_MQ_F_SHOULD_MERGE ; + md->tag_set->flags =BLK_MQ_F_SHOULD_MERGE |BLK_MQ_F_NO_MANAGED_IRQ ; md->tag_set->nr_hw_queues =dm_get_blk_mq_nr_hw_queues (); md->tag_set->driver_data = md;include/linux/blk-mq.h +3
-0@@ -140,6 +140,8 @@ struct blk_mq_hw_ctx {*/ atomic_t nr_active; +/** @cpuhp_online: List to store request if CPU is going to die */ +struct hlist_node cpuhp_online;/** @cpuhp_dead: List to store request if some CPU die. */ struct hlist_node cpuhp_dead;/** @kobj: Kernel object for sysfs. */ @@ -391,6 +393,7 @@ struct blk_mq_ops {enum {BLK_MQ_F_SHOULD_MERGE =1 <<0 ,BLK_MQ_F_TAG_SHARED =1 <<1 , +BLK_MQ_F_NO_MANAGED_IRQ =1 <<2 ,BLK_MQ_F_BLOCKING =1 <<5 ,BLK_MQ_F_NO_SCHED =1 <<6 ,BLK_MQ_F_ALLOC_POLICY_START_BIT =8 ,include/linux/cpuhotplug.h +0
-0include/linux/cpuhotplug.h enum cpuhp_state { · line 158
Quoted 7 lines
include/linux/cpuhotplug.h +1
-0@@ -152,6 +152,7 @@ enum cpuhp_state {CPUHP_AP_SMPBOOT_THREADS ,CPUHP_AP_X86_VDSO_VMA_ONLINE ,CPUHP_AP_IRQ_AFFINITY_ONLINE , +CPUHP_AP_BLK_MQ_ONLINE ,CPUHP_AP_ARM_MVEBU_SYNC_CLOCKS ,CPUHP_AP_X86_INTEL_EPB_ONLINE , CPUHP_AP_PERF_ONLINE,Ho-hum.
I do agree for the loop and the CPUHP part (not that I'm qualified to just the latter, but anyway).
For the dm side I'm less certain.
Thing is, we rarely get hardware interrupts directly to the device-mapper device, but rather to the underlying hardware LLD.
I even not quite sure what exactly the implications of managed interrupts with dm are; after all, we're using softirqs here, don't we?
Quoted 4 lines
So for DM I'd rather wait for the I/O on the underlying devices' hctx to become quiesce, and not kill them ourselves.
Not sure if the device-mapper framework _can_ do this right now, though. Mike?
The problem the patchset tries to address is drivers applying managed interrupt. When all CPUs of one managed interrupt line are offline, the IO interrupt may be never to trigger, so IO timeout may be triggered or IO hang if no timeout handler is provided.
So any drivers which don't use managed interrupt can be marked as BLK_MQ_F_NO_MANAGED_IRQ.
For dm-rq, request completion is always triggered by underlying request, so once underlying request is guaranteed to be completed, dm-rq's request can be completed too.
Thanks,
Ming
PATCH v8 7/11 blk-mq: stop to handle IO and drain IO before hctx becomes inactive
In reply to Ming LeiBefore one CPU becomes offline, check if it is the last online CPU of hctx. If yes, mark this hctx as inactive, meantime wait for completion of all in-flight IOs originated from this hctx. Meantime check if this hctx has become inactive in blk_mq_get_driver_tag(), if yes, release the allocated tag.
This way guarantees that there isn't any inflight IO before shutdowning the managed IRQ line when all CPUs of this IRQ line is offline.
--- block/blk-mq-debugfs.c | 1 + block/blk-mq.c | 124 +++++++++++++++++++++++++++++++++++++---- include/linux/blk-mq.h | 3 + 3 files changed, 117 insertions(+), 11 deletions(-)
block/blk-mq-debugfs.c +1 -0
@@ -213,6 +213,7 @@ static const char *const hctx_state_name[] = {HCTX_STATE_NAME (STOPPED ),HCTX_STATE_NAME (TAG_ACTIVE ),HCTX_STATE_NAME (SCHED_RESTART ), + HCTX_STATE_NAME(INACTIVE), };#undef HCTX_STATE_NAME
block/blk-mq.c +113 -11
184 lines not on this page · raw message
include/linux/blk-mq.h +3 -0
@@ -403,6 +403,9 @@ enum {BLK_MQ_S_TAG_ACTIVE =1 ,BLK_MQ_S_SCHED_RESTART =2 , +/* hw queue is inactive after all its CPUs become offline */ +BLK_MQ_S_INACTIVE =3 , +BLK_MQ_MAX_DEPTH =10240 , BLK_MQ_CPU_WORK_BATCH = 8,
Signature · 1 line
2.25.2
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 8 lines · Ming Lei
Before one CPU becomes offline, check if it is the last online CPU of hctx. If yes, mark this hctx as inactive, meantime wait for completion of all in-flight IOs originated from this hctx. Meantime check if this hctx has become inactive in
blk_mq_get_driver_tag(), if yes, release the allocated tag.This way guarantees that there isn't any inflight IO before shutdowning the managed IRQ line when all CPUs of this IRQ line is offline.
Can you take a look at all my comments on the previous version here (splitting blk_mq_get_driver_tag for direct_issue vs not, what is the point of barrier(), smp_mb__before_atomic and smp_mb__after_atomic), as none seems to be addressed and I also didn't see a reply.
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 7 lines · Christoph Hellwig
Quoted 6 lines · Ming Lei
Before one CPU becomes offline, check if it is the last online CPU of hctx. If yes, mark this hctx as inactive, meantime wait for completion of all in-flight IOs originated from this hctx. Meantime check if this hctx has become inactive in
blk_mq_get_driver_tag(), if yes, release the allocated tag.
Quoted 5 lines
Quoted 2 lines
This way guarantees that there isn't any inflight IO before shutdowning the managed IRQ line when all CPUs of this IRQ line is offline.
Can you take a look at all my comments on the previous version here (splitting
blk_mq_get_driver_tagfordirect_issuevs not, what is
I am not sure if it helps by adding two helper, given only two parameters are needed, and the new parameter is just a constant.
Quoted 3 lines
the point of
barrier(),smp_mb__before_atomicandsmp_mb__after_atomic), as none seems to be addressed and I also didn't see a reply.
I believe it has been documented:
+ /*
+ * Add one memory barrier in case that direct issue IO process is + * migrated to other CPU which may not belong to this hctx, so we can + * order driver tag assignment and checking BLK_MQ_S_INACTIVE. + * Otherwise, barrier() is enough given both setting BLK_MQ_S_INACTIVE + * and driver tag assignment are run on the same CPU in case that + * BLK_MQ_S_INACTIVE is set. + */
OK, I can add more:
In case of not direct issue, __blk_mq_delay_run_hw_queue() guarantees that dispatch is done on CPUs of this hctx.
In case of direct issue, the direct issue IO process may be migrated to other CPU which doesn't belong to hctx->cpumask even though the chance is quite small, but still possible.
This patch sets hctx as inactive in the last CPU of hctx, so barrier() is enough for not direct issue. Otherwise, one smp_mb() is added for ordering tag assignment(include setting rq) and checking S_INACTIVE in blk_mq_get_driver_tag().
Thanks,
Ming
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 23 lines · Ming Lei
I am not sure if it helps by adding two helper, given only two parameters are needed, and the new parameter is just a constant.
Quoted 3 lines
the point of
barrier(),smp_mb__before_atomicandsmp_mb__after_atomic), as none seems to be addressed and I also didn't see a reply.I believe it has been documented:
block/blk-mq.c +8
-0+/* +* Add one memory barrier in case that direct issue IO process is +* migrated to other CPU which may not belong to this hctx, so we can +* order driver tag assignment and checking BLK_MQ_S_INACTIVE. +* Otherwise, barrier() is enough given both setting BLK_MQ_S_INACTIVE +* and driver tag assignment are run on the same CPU in case that +* BLK_MQ_S_INACTIVE is set. +*/ OK, I can add more:
In case of not direct issue,
__blk_mq_delay_run_hw_queue()guarantees that dispatch is done on CPUs of this hctx.
Quoted 8 lines
In case of direct issue, the direct issue IO process may be migrated to other CPU which doesn't belong to
hctx->cpumaskeven though the chance is quite small, but still possible.This patch sets hctx as inactive in the last CPU of hctx, so
barrier()is enough for not direct issue. Otherwise, onesmp_mb()is added for ordering tag assignment(include setting rq) and checkingS_INACTIVEinblk_mq_get_driver_tag().
How do you prevent a cpu migration between the call to raw_smp_processor_id and barrier?
Also as far as I can tell Documentation/core-api/atomic_ops.rst ask you to use smp_mb__before_atomic and smp_mb__after_atomic for any ordering with non-updating bitops. Quote:
--------------------------------- snip --------------------------------- If explicit memory barriers are required around {set,clear}_bit() (which do not return a value, and thus does not need to provide memory barrier semantics), two interfaces are provided::
void smp_mb__before_atomic(void); void smp_mb__after_atomic(void);
--------------------------------- snip ---------------------------------
I really want someone who knows the memory model to look over this scheme, as it looks dangerous.
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 28 lines · Christoph Hellwig
Quoted 27 lines · Ming Lei
I am not sure if it helps by adding two helper, given only two parameters are needed, and the new parameter is just a constant.
Quoted 3 lines
the point of
barrier(),smp_mb__before_atomicandsmp_mb__after_atomic), as none seems to be addressed and I also didn't see a reply.I believe it has been documented:
block/blk-mq.c +8
-0+/* +* Add one memory barrier in case that direct issue IO process is +* migrated to other CPU which may not belong to this hctx, so we can +* order driver tag assignment and checking BLK_MQ_S_INACTIVE. +* Otherwise, barrier() is enough given both setting BLK_MQ_S_INACTIVE +* and driver tag assignment are run on the same CPU in case that +* BLK_MQ_S_INACTIVE is set. +*/ OK, I can add more:
In case of not direct issue,
__blk_mq_delay_run_hw_queue()guarantees that dispatch is done on CPUs of this hctx.In case of direct issue, the direct issue IO process may be migrated to other CPU which doesn't belong to
hctx->cpumaskeven though the chance is quite small, but still possible.
Quoted 7 lines
Quoted 4 lines
This patch sets hctx as inactive in the last CPU of hctx, so
barrier()is enough for not direct issue. Otherwise, onesmp_mb()is added for ordering tag assignment(include setting rq) and checkingS_INACTIVEinblk_mq_get_driver_tag().How do you prevent a cpu migration between the call to
raw_smp_processor_idand barrier?
Fine, we may have to use get_cpu()/put_cpu() for direct issue to cover the check. For non-direct issue, either preempt is disabled or the work is run on specified CPU.
Quoted 10 lines
Also as far as I can tell
Documentation/core-api/atomic_ops.rstask you to usesmp_mb__before_atomicandsmp_mb__after_atomicfor any ordering with non-updating bitops. Quote:--------------------------------- snip --------------------------------- If explicit memory barriers are required around {set,clear}_bit() (which do not return a value, and thus does not need to provide memory barrier semantics), two interfaces are provided::
Quoted 6 lines
void smp_mb__before_atomic(void); void smp_mb__after_atomic(void);--------------------------------- snip ---------------------------------
I really want someone who knows the memory model to look over this scheme, as it looks dangerous.
smp_mb() is enough, the version of _[before|after]_atomic might be a little lightweight in some ARCH I guess. Given smp_mb() or its variant is only needed in very unlikely case of slow path, it is fine to just use smp_mb(), IMO.
Thanks,
Ming
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 55 lines · Ming Lei
Quoted 28 lines · Christoph Hellwig
Quoted 27 lines · Ming Lei
I am not sure if it helps by adding two helper, given only two parameters are needed, and the new parameter is just a constant.
Quoted 3 lines
the point of
barrier(),smp_mb__before_atomicandsmp_mb__after_atomic), as none seems to be addressed and I also didn't see a reply.I believe it has been documented:
block/blk-mq.c +8
-0+/* +* Add one memory barrier in case that direct issue IO process is +* migrated to other CPU which may not belong to this hctx, so we can +* order driver tag assignment and checking BLK_MQ_S_INACTIVE. +* Otherwise, barrier() is enough given both setting BLK_MQ_S_INACTIVE +* and driver tag assignment are run on the same CPU in case that +* BLK_MQ_S_INACTIVE is set. +*/ OK, I can add more:
In case of not direct issue,
__blk_mq_delay_run_hw_queue()guarantees that dispatch is done on CPUs of this hctx.In case of direct issue, the direct issue IO process may be migrated to other CPU which doesn't belong to
hctx->cpumaskeven though the chance is quite small, but still possible.Quoted 7 lines
Quoted 4 lines
This patch sets hctx as inactive in the last CPU of hctx, so
barrier()is enough for not direct issue. Otherwise, onesmp_mb()is added for ordering tag assignment(include setting rq) and checkingS_INACTIVEinblk_mq_get_driver_tag().How do you prevent a cpu migration between the call to
raw_smp_processor_idand barrier?Fine, we may have to use get_cpu()/put_cpu() for direct issue to cover the check. For non-direct issue, either preempt is disabled or the work is run on specified CPU.
Quoted 14 lines
Also as far as I can tell
Documentation/core-api/atomic_ops.rstask you to usesmp_mb__before_atomicandsmp_mb__after_atomicfor any ordering with non-updating bitops. Quote:--------------------------------- snip --------------------------------- If explicit memory barriers are required around {set,clear}_bit() (which do not return a value, and thus does not need to provide memory barrier semantics), two interfaces are provided::
void smp_mb__before_atomic(void); void smp_mb__after_atomic(void);--------------------------------- snip ---------------------------------
Quoted 6 lines
Quoted 2 lines
I really want someone who knows the memory model to look over this scheme, as it looks dangerous.
smp_mb()is enough, the version of _[before|after]_atomic might be a little lightweight in some ARCH I guess. Givensmp_mb()or its variant is only needed in very unlikely case of slow path, it is fine to just
s/of/or
Thanks,
Ming
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
FYI, here is what I think we should be doing (but the memory model experts please correct me):
- just drop the direct_issue flag and check for the CPU, which is cheap enough
- replace the raw_smp_processor_id with a get_cpu to make sure we don't hit the tiny migration windows
- a bunch of random cleanups to make the code easier to read, mostly by being more self-documenting or improving the comments.
block/blk-mq.c +34 -44
@@ -1049,28 +1049,16 @@ static bool __blk_mq_get_driver_tag(struct request *rq)atomic_inc (&data.hctx->nr_active); } data.hctx->tags->rqs[rq->tag] = rq; -return true; -} - -static bool blk_mq_get_driver_tag (struct request *rq,bool direct_issue) -{ -if (rq->tag !=-1 ) -return true; -if (!__blk_mq_get_driver_tag (rq)) -return false;/* -* Add one memory barrier in case that direct issue IO process is -* migrated to other CPU which may not belong to this hctx, so we can -* order driver tag assignment and checking BLK_MQ_S_INACTIVE. -* Otherwise, barrier() is enough given both setting BLK_MQ_S_INACTIVE -* and driver tag assignment are run on the same CPU in case that -* BLK_MQ_S_INACTIVE is set. +* Ensure updates to rq->tag and tags->rqs[] are seen by +* blk_mq_tags_inflight_rqs. This pairs with the smp_mb__after_atomic +* in blk_mq_hctx_notify_offline. This only matters in case a process +* gets migrated to another CPU that is not mapped to this hctx. */ -if (unlikely (direct_issue && rq->mq_ctx->cpu !=raw_smp_processor_id ())) +if (rq->mq_ctx->cpu !=get_cpu ())smp_mb (); -else -barrier (); +put_cpu ();if (unlikely (test_bit (BLK_MQ_S_INACTIVE , &rq->mq_hctx->state))) {blk_mq_put_driver_tag (rq);
@@ -1079,6 +1067,13 @@ static bool blk_mq_get_driver_tag(struct request *rq, bool direct_issue)return true; } +static bool blk_mq_get_driver_tag (struct request *rq) +{ +if (rq->tag !=-1 ) +return true; +return __blk_mq_get_driver_tag (rq); +} +static int blk_mq_dispatch_wake (wait_queue_entry_t *wait,unsigned mode,int flags,void *key) {
@@ -1125,7 +1120,7 @@ static bool blk_mq_mark_tag_wait(struct blk_mq_hw_ctx *hctx,* Don't clear RESTART here, someone else could have set it. * At most this will cost an extra queue run. */ -return blk_mq_get_driver_tag (rq, false); +return blk_mq_get_driver_tag (rq); } wait = &hctx->dispatch_wait;
@@ -1151,7 +1146,7 @@ static bool blk_mq_mark_tag_wait(struct blk_mq_hw_ctx *hctx,* allocation failure and adding the hardware queue to the wait * queue. */ - ret =blk_mq_get_driver_tag (rq, false); + ret =blk_mq_get_driver_tag (rq);if (!ret) {spin_unlock (&hctx->dispatch_wait_lock);spin_unlock_irq (&wq->lock);
@@ -1252,7 +1247,7 @@ bool blk_mq_dispatch_rq_list(struct request_queue *q, struct list_head *list,break ; } -if (!blk_mq_get_driver_tag (rq, false)) { +if (!blk_mq_get_driver_tag (rq)) {/* * The initial allocation attempt failed, so we need to * rerun the hardware queue when a tag is freed. The
@@ -1284,7 +1279,7 @@ bool blk_mq_dispatch_rq_list(struct request_queue *q, struct list_head *list, bd.last = true; else { nxt = list_first_entry(list, struct request, queuelist); - bd.last = !blk_mq_get_driver_tag (nxt, false); + bd.last = !blk_mq_get_driver_tag (nxt); } ret = q->mq_ops->queue_rq (hctx, &bd);
@@ -1886,7 +1881,7 @@ static blk_status_t __blk_mq_try_issue_directly(struct blk_mq_hw_ctx *hctx,if (!blk_mq_get_dispatch_budget (hctx)) goto insert; -if (!blk_mq_get_driver_tag (rq, true)) { +if (!blk_mq_get_driver_tag (rq)) {blk_mq_put_dispatch_budget (hctx); goto insert; }
@@ -2327,23 +2322,24 @@ static bool blk_mq_inflight_rq(struct request *rq, void *data,static unsigned blk_mq_tags_inflight_rqs (struct blk_mq_hw_ctx *hctx) {struct count_inflight_data count_data = { - .count =0 , .hctx = hctx, };blk_mq_all_tag_busy_iter (hctx->tags, blk_mq_count_inflight_rq, blk_mq_inflight_rq, &count_data); -return count_data.count; } -static void blk_mq_hctx_drain_inflight_rqs (struct blk_mq_hw_ctx *hctx) +static inline bool blk_mq_last_cpu_in_hctx (unsigned int cpu, +struct blk_mq_hw_ctx *hctx) { -while (1 ) { -if (!blk_mq_tags_inflight_rqs (hctx)) -break ; -msleep (5 ); - } +if (!cpumask_test_cpu (cpu, hctx->cpumask)) +return false; +if (cpumask_next_and (-1 , hctx->cpumask, cpu_online_mask) != cpu) +return false; +if (cpumask_next_and (cpu, hctx->cpumask, cpu_online_mask) < nr_cpu_ids) +return false; +return true; }static int blk_mq_hctx_notify_offline (unsigned int cpu,struct hlist_node *node)
@@ -2351,25 +2347,19 @@ static int blk_mq_hctx_notify_offline(unsigned int cpu, struct hlist_node *node)struct blk_mq_hw_ctx *hctx =hlist_entry_safe (node, struct blk_mq_hw_ctx, cpuhp_online); -if (!cpumask_test_cpu (cpu, hctx->cpumask)) -return 0 ; - -if ((cpumask_next_and (-1 , hctx->cpumask, cpu_online_mask) != cpu) || - (cpumask_next_and (cpu, hctx->cpumask, cpu_online_mask) < nr_cpu_ids)) +if (!blk_mq_last_cpu_in_hctx (cpu, hctx))return 0 ;/* -* The current CPU is the last one in this hctx, S_INACTIVE -* can be observed in dispatch path without any barrier needed, -* cause both are run on one same CPU. +* Order setting BLK_MQ_S_INACTIVE versus checking rq->tag and rqs[tag], +* in blk_mq_tags_inflight_rqs. It pairs with the smp_mb() in +* blk_mq_get_driver_tag. */ set_bit (BLK_MQ_S_INACTIVE , &hctx->state); -/* -* Order setting BLK_MQ_S_INACTIVE and checking rq->tag & rqs[tag], -* and its pair is the smp_mb() in blk_mq_get_driver_tag -*/ smp_mb__after_atomic (); -blk_mq_hctx_drain_inflight_rqs (hctx); + +while (blk_mq_tags_inflight_rqs (hctx)) +msleep (5 );return 0 ; }
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 5 lines · Christoph Hellwig
FYI, here is what I think we should be doing (but the memory model experts please correct me):
- just drop the
direct_issueflag and check for the CPU, which is cheap enough
That isn't correct because the CPU for running async queue may not be same with rq->mq_ctx->cpu since hctx->cpumask may include several CPUs and we run queue in RR style and it is really a normal case.
So I'd rather to keep 'direct_issue' flag given it is just a constant argument and gcc is smart enough to optimize this case if you don't have better idea.
Quoted 2 lines
- replace the
raw_smp_processor_idwith aget_cputo make sure we don't hit the tiny migration windows
Will do that.
Quoted 2 lines
- a bunch of random cleanups to make the code easier to read, mostly by being more self-documenting or improving the comments.
The cleanup code looks fine.
Thanks,
Ming
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 3 lines · Ming Lei
Quoted 2 lines · Christoph Hellwig
FYI, here is what I think we should be doing (but the memory model experts please correct me):
Hi Ming,
Quoted 9 lines
Quoted 3 lines
- just drop the
direct_issueflag and check for the CPU, which is cheap enoughThat isn't correct because the CPU for running async queue may not be same with
rq->mq_ctx->cpusincehctx->cpumaskmay include several CPUs and we run queue in RR style and it is really a normal case.So I'd rather to keep '
direct_issue' flag given it is just a constant
How about changing the function argument name from 'direct_issue' to something which better expresses the intent, like 'may_migrate' or similar? (I know you mention the reason this in the comment also).
Quoted 6 lines
argument and gcc is smart enough to optimize this case if you don't have better idea.
Quoted 2 lines
- replace the
raw_smp_processor_idwith aget_cputo make sure we don't hit the tiny migration windows
I do wonder if the barrier always may be cheaper than this.
Quoted 8 lines
Will do that.
Quoted 2 lines
- a bunch of random cleanups to make the code easier to read, mostly by being more self-documenting or improving the comments.
The cleanup code looks fine.
Cheers,
John
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
In reply to Ming LeiQuoted 10 lines · Ming Lei
Quoted 5 lines · Christoph Hellwig
FYI, here is what I think we should be doing (but the memory model experts please correct me):
- just drop the
direct_issueflag and check for the CPU, which is cheap enoughThat isn't correct because the CPU for running async queue may not be same with
rq->mq_ctx->cpusincehctx->cpumaskmay include several CPUs and we run queue in RR style and it is really a normal case.
But in that case the memory barrier really doesn't matter anywaẏ.
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 5 lines · Christoph Hellwig
Quoted 4 lines · Ming Lei
Quoted 3 lines · Christoph Hellwig
FYI, here is what I think we should be doing (but the memory model experts please correct me):
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines
- just drop the
direct_issueflag and check for the CPU, which is cheap enoughThat isn't correct because the CPU for running async queue may not be same with
rq->mq_ctx->cpusincehctx->cpumaskmay include several CPUs and we run queue in RR style and it is really a normal case.But in that case the memory barrier really doesn't matter anywaẏ.
It might be true, however we can save the cost with zero cost, why not do it? Also with document benefit.
Thanks,
Ming
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
In reply to Christoph HellwigQuoted 2 lines · Christoph Hellwig
FYI, here is what I think we should be doing (but the memory model experts please correct me):
I would be happy to, but could you please tell me what to apply this against? I made several wrong guesses, and am not familiar enough with this code to evaluate this patch in isolation.
Thanx, Paul
Quoted 171 lines
- just drop the
direct_issueflag and check for the CPU, which is cheap enough
- replace theraw_smp_processor_idwith aget_cputo make sure we don't hit the tiny migration windows
- a bunch of random cleanups to make the code easier to read, mostly by being more self-documenting or improving the comments.block/blk-mq.c +34
-44@@ -1049,28 +1049,16 @@ static bool __blk_mq_get_driver_tag(struct request *rq)atomic_inc (&data.hctx->nr_active); } data.hctx->tags->rqs[rq->tag] = rq; -return true; -} - -static bool blk_mq_get_driver_tag (struct request *rq,bool direct_issue) -{ -if (rq->tag !=-1 ) -return true; -if (!__blk_mq_get_driver_tag (rq)) -return false;/* -* Add one memory barrier in case that direct issue IO process is -* migrated to other CPU which may not belong to this hctx, so we can -* order driver tag assignment and checking BLK_MQ_S_INACTIVE. -* Otherwise, barrier() is enough given both setting BLK_MQ_S_INACTIVE -* and driver tag assignment are run on the same CPU in case that -* BLK_MQ_S_INACTIVE is set. +* Ensure updates to rq->tag and tags->rqs[] are seen by +* blk_mq_tags_inflight_rqs. This pairs with the smp_mb__after_atomic +* in blk_mq_hctx_notify_offline. This only matters in case a process +* gets migrated to another CPU that is not mapped to this hctx. */ -if (unlikely (direct_issue && rq->mq_ctx->cpu !=raw_smp_processor_id ())) +if (rq->mq_ctx->cpu !=get_cpu ())smp_mb (); -else -barrier (); +put_cpu ();if (unlikely (test_bit (BLK_MQ_S_INACTIVE , &rq->mq_hctx->state))) {blk_mq_put_driver_tag (rq);@@ -1079,6 +1067,13 @@ static bool blk_mq_get_driver_tag(struct request *rq, bool direct_issue)return true; } +static bool blk_mq_get_driver_tag (struct request *rq) +{ +if (rq->tag !=-1 ) +return true; +return __blk_mq_get_driver_tag (rq); +} +static int blk_mq_dispatch_wake (wait_queue_entry_t *wait,unsigned mode,int flags,void *key) {@@ -1125,7 +1120,7 @@ static bool blk_mq_mark_tag_wait(struct blk_mq_hw_ctx *hctx,* Don't clear RESTART here, someone else could have set it. * At most this will cost an extra queue run. */ -return blk_mq_get_driver_tag (rq, false); +return blk_mq_get_driver_tag (rq); } wait = &hctx->dispatch_wait;@@ -1151,7 +1146,7 @@ static bool blk_mq_mark_tag_wait(struct blk_mq_hw_ctx *hctx,* allocation failure and adding the hardware queue to the wait * queue. */ - ret =blk_mq_get_driver_tag (rq, false); + ret =blk_mq_get_driver_tag (rq);if (!ret) {spin_unlock (&hctx->dispatch_wait_lock);spin_unlock_irq (&wq->lock);@@ -1252,7 +1247,7 @@ bool blk_mq_dispatch_rq_list(struct request_queue *q, struct list_head *list,break ; } -if (!blk_mq_get_driver_tag (rq, false)) { +if (!blk_mq_get_driver_tag (rq)) {/* * The initial allocation attempt failed, so we need to * rerun the hardware queue when a tag is freed. The @@ -1284,7 +1279,7 @@ bool blk_mq_dispatch_rq_list(struct request_queue *q, struct list_head *list, bd.last = true; else { nxt = list_first_entry(list, struct request, queuelist); - bd.last = !blk_mq_get_driver_tag (nxt, false); + bd.last = !blk_mq_get_driver_tag (nxt); } ret = q->mq_ops->queue_rq (hctx, &bd);@@ -1886,7 +1881,7 @@ static blk_status_t __blk_mq_try_issue_directly(struct blk_mq_hw_ctx *hctx,if (!blk_mq_get_dispatch_budget (hctx)) goto insert; -if (!blk_mq_get_driver_tag (rq, true)) { +if (!blk_mq_get_driver_tag (rq)) {blk_mq_put_dispatch_budget (hctx); goto insert; }@@ -2327,23 +2322,24 @@ static bool blk_mq_inflight_rq(struct request *rq, void *data,static unsigned blk_mq_tags_inflight_rqs (struct blk_mq_hw_ctx *hctx) {struct count_inflight_data count_data = { - .count =0 , .hctx = hctx, };blk_mq_all_tag_busy_iter (hctx->tags, blk_mq_count_inflight_rq, blk_mq_inflight_rq, &count_data); -return count_data.count; } -static void blk_mq_hctx_drain_inflight_rqs (struct blk_mq_hw_ctx *hctx) +static inline bool blk_mq_last_cpu_in_hctx (unsigned int cpu, +struct blk_mq_hw_ctx *hctx) { -while (1 ) { -if (!blk_mq_tags_inflight_rqs (hctx)) -break ; -msleep (5 ); - } +if (!cpumask_test_cpu (cpu, hctx->cpumask)) +return false; +if (cpumask_next_and (-1 , hctx->cpumask, cpu_online_mask) != cpu) +return false; +if (cpumask_next_and (cpu, hctx->cpumask, cpu_online_mask) < nr_cpu_ids) +return false; +return true; }static int blk_mq_hctx_notify_offline (unsigned int cpu,struct hlist_node *node)@@ -2351,25 +2347,19 @@ static int blk_mq_hctx_notify_offline(unsigned int cpu, struct hlist_node *node)struct blk_mq_hw_ctx *hctx =hlist_entry_safe (node, struct blk_mq_hw_ctx, cpuhp_online); -if (!cpumask_test_cpu (cpu, hctx->cpumask)) -return 0 ; - -if ((cpumask_next_and (-1 , hctx->cpumask, cpu_online_mask) != cpu) || - (cpumask_next_and (cpu, hctx->cpumask, cpu_online_mask) < nr_cpu_ids)) +if (!blk_mq_last_cpu_in_hctx (cpu, hctx))return 0 ;/* -* The current CPU is the last one in this hctx, S_INACTIVE -* can be observed in dispatch path without any barrier needed, -* cause both are run on one same CPU. +* Order setting BLK_MQ_S_INACTIVE versus checking rq->tag and rqs[tag], +* in blk_mq_tags_inflight_rqs. It pairs with the smp_mb() in +* blk_mq_get_driver_tag. */ set_bit (BLK_MQ_S_INACTIVE , &hctx->state); -/* -* Order setting BLK_MQ_S_INACTIVE and checking rq->tag & rqs[tag], -* and its pair is the smp_mb() in blk_mq_get_driver_tag -*/ smp_mb__after_atomic (); -blk_mq_hctx_drain_inflight_rqs (hctx); + +while (blk_mq_tags_inflight_rqs (hctx)) +msleep (5 );return 0 ; }
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 7 lines · Paul E. McKenney
Quoted 2 lines · Christoph Hellwig
FYI, here is what I think we should be doing (but the memory model experts please correct me):
I would be happy to, but could you please tell me what to apply this against? I made several wrong guesses, and am not familiar enough with this code to evaluate this patch in isolation.
Here is a link to the whole series on lore:
Peter Zijlstra
maintainerRe: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
In reply to Christoph Hellwigblock/blk-mq.c static bool __blk_mq_get_driver_tag(struct request *rq) · line 1061
Quoted 13 lines · Christoph Hellwig
block/blk-mq.c +6
-0atomic_inc (&data.hctx->nr_active); } data.hctx->tags->rqs[rq->tag] = rq;/* +* Ensure updates to rq->tag and tags->rqs[] are seen by +* blk_mq_tags_inflight_rqs. This pairs with the smp_mb__after_atomic +* in blk_mq_hctx_notify_offline. This only matters in case a process +* gets migrated to another CPU that is not mapped to this hctx. */ +if (rq->mq_ctx->cpu !=get_cpu ())smp_mb (); +put_cpu ();
This looks exceedingly weird; how do you think you can get to another CPU and not have an smp_mb() implied in the migration itself? Also, what stops the migration from happening right after the put_cpu() ?
Quoted 5 lines
block/blk-mq.c +1
-0if (unlikely (test_bit (BLK_MQ_S_INACTIVE , &rq->mq_hctx->state))) {blk_mq_put_driver_tag (rq); +static inline bool blk_mq_last_cpu_in_hctx(unsigned int cpu,
block/blk-mq.c static bool blk_mq_inflight_rq(struct request *rq, void *data, · line 2343
Quoted 10 lines
block/blk-mq.c +8
-0+ struct blk_mq_hw_ctx *hctx) { +if (!cpumask_test_cpu (cpu, hctx->cpumask)) +return false; +if (cpumask_next_and (-1 , hctx->cpumask, cpu_online_mask) != cpu) +return false; +if (cpumask_next_and (cpu, hctx->cpumask, cpu_online_mask) < nr_cpu_ids) +return false; +return true; }
Does this want something like:
lockdep_assert_held(*set->tag_list_lock);
to make sure hctx->cpumask is stable? Those mask ops are not stable vs concurrenct set/clear at all.
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Hi Peter,
Quoted 5 lines · Peter Zijlstra
Quoted 4 lines · Christoph Hellwig
block/blk-mq.c +0
-0atomic_inc (&data.hctx->nr_active); } data.hctx->tags->rqs[rq->tag] = rq;
Quoted 12 lines
block/blk-mq.c static bool __blk_mq_get_driver_tag(struct request *rq) · line 1061
Quoted 9 lines
block/blk-mq.c +6
-0/* +* Ensure updates to rq->tag and tags->rqs[] are seen by +* blk_mq_tags_inflight_rqs. This pairs with the smp_mb__after_atomic +* in blk_mq_hctx_notify_offline. This only matters in case a process +* gets migrated to another CPU that is not mapped to this hctx. */ +if (rq->mq_ctx->cpu !=get_cpu ())smp_mb (); +put_cpu ();This looks exceedingly weird; how do you think you can get to another CPU and not have an
smp_mb()implied in the migration itself? Also, what
What we need is one smp_mb() between the following two OPs:
1)
rq->tag = rq->internal_tag;
data.hctx->tags->rqs[rq->tag] = rq;
2)
if (unlikely(test_bit(BLK_MQ_S_INACTIVE, &rq->mq_hctx->state)))
And the pair of the above barrier is in blk_mq_hctx_notify_offline().
So if this process is migrated before 1), the implied smp_mb() is useless.
Quoted 1 line
stops the migration from happening right after the
put_cpu()?
If the migration happens after put_cpu(), the above two OPs are still ordered by the implied smp_mb(), so looks not a problem.
Quoted 20 lines
Quoted 7 lines
block/blk-mq.c +1
-0if (unlikely (test_bit (BLK_MQ_S_INACTIVE , &rq->mq_hctx->state))) {blk_mq_put_driver_tag (rq); +static inline bool blk_mq_last_cpu_in_hctx(unsigned int cpu,block/blk-mq.c static bool blk_mq_inflight_rq(struct request *rq, void *data, · line 2343
Quoted 10 lines
block/blk-mq.c +8
-0+ struct blk_mq_hw_ctx *hctx) { +if (!cpumask_test_cpu (cpu, hctx->cpumask)) +return false; +if (cpumask_next_and (-1 , hctx->cpumask, cpu_online_mask) != cpu) +return false; +if (cpumask_next_and (cpu, hctx->cpumask, cpu_online_mask) < nr_cpu_ids) +return false; +return true; }Does this want something like:
Quoted 4 lines
lockdep_assert_held(*set->tag_list_lock);to make sure
hctx->cpumaskis stable? Those mask ops are not stable vs concurrenct set/clear at all.
hctx->cpumask is only updated in __blk_mq_update_nr_hw_queues(), in which all request queues in the tagset have been frozen, and no any in-flight IOs, so we needn't to pay attention to that case.
Thanks,
Ming
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 21 lines · Ming Lei
Quoted 5 lines · Peter Zijlstra
Quoted 4 lines · Christoph Hellwig
block/blk-mq.c +0
-0atomic_inc (&data.hctx->nr_active); } data.hctx->tags->rqs[rq->tag] = rq;Quoted 12 lines
block/blk-mq.c static bool __blk_mq_get_driver_tag(struct request *rq) · line 1061
Quoted 9 lines
block/blk-mq.c +6
-0/* +* Ensure updates to rq->tag and tags->rqs[] are seen by +* blk_mq_tags_inflight_rqs. This pairs with the smp_mb__after_atomic +* in blk_mq_hctx_notify_offline. This only matters in case a process +* gets migrated to another CPU that is not mapped to this hctx. */ +if (rq->mq_ctx->cpu !=get_cpu ())smp_mb (); +put_cpu ();This looks exceedingly weird; how do you think you can get to another CPU and not have an
smp_mb()implied in the migration itself? Also, whatWhat we need is one
smp_mb()between the following two OPs:
Quoted 8 lines
1)
rq->tag = rq->internal_tag; data.hctx->tags->rqs[rq->tag] = rq;2)
if (unlikely(test_bit(BLK_MQ_S_INACTIVE, &rq->mq_hctx->state)))And the pair of the above barrier is in
blk_mq_hctx_notify_offline().
I'm struggling with this, so let me explain why. My understanding of the original patch [1] and your explanation above is that you want *either* of the following behaviours
- __blk_mq_get_driver_tag() (i.e. (1) above) and test_bit(BLK_MQ_S_INACTIVE, ...) run on the same CPU with barrier() between them, or
- There is a migration and therefore an implied smp_mb() between them
However, given that most CPUs can speculate loads (and therefore the test_bit() operation), I don't understand how the "everything runs on the same CPU" is safe if a barrier() is required. In other words, if the barrier() is needed to prevent the compiler hoisting the load, then the CPU can still cause problems.
Thanks,
Will
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 38 lines · Will Deacon
Quoted 21 lines · Ming Lei
Quoted 5 lines · Peter Zijlstra
Quoted 4 lines · Christoph Hellwig
block/blk-mq.c +0
-0atomic_inc (&data.hctx->nr_active); } data.hctx->tags->rqs[rq->tag] = rq;Quoted 12 lines
block/blk-mq.c static bool __blk_mq_get_driver_tag(struct request *rq) · line 1061
Quoted 9 lines
block/blk-mq.c +6
-0/* +* Ensure updates to rq->tag and tags->rqs[] are seen by +* blk_mq_tags_inflight_rqs. This pairs with the smp_mb__after_atomic +* in blk_mq_hctx_notify_offline. This only matters in case a process +* gets migrated to another CPU that is not mapped to this hctx. */ +if (rq->mq_ctx->cpu !=get_cpu ())smp_mb (); +put_cpu ();This looks exceedingly weird; how do you think you can get to another CPU and not have an
smp_mb()implied in the migration itself? Also, whatWhat we need is one
smp_mb()between the following two OPs:Quoted 8 lines
1)
rq->tag = rq->internal_tag; data.hctx->tags->rqs[rq->tag] = rq;2)
if (unlikely(test_bit(BLK_MQ_S_INACTIVE, &rq->mq_hctx->state)))And the pair of the above barrier is in
blk_mq_hctx_notify_offline().I'm struggling with this, so let me explain why. My understanding of the original patch [1] and your explanation above is that you want *either* of the following behaviours
-
__blk_mq_get_driver_tag()(i.e. (1) above) andtest_bit(BLK_MQ_S_INACTIVE, ...)run on the same CPU withbarrier()between them, or
Quoted 7 lines
- There is a migration and therefore an implied
smp_mb()between themHowever, given that most CPUs can speculate loads (and therefore the
test_bit()operation), I don't understand how the "everything runs on the same CPU" is safe if abarrier()is required. In other words, if thebarrier()is needed to prevent the compiler hoisting the load, then the CPU can still cause problems.
Do you think the speculate loads may return wrong value of BLK_MQ_S_INACTIVE bit in case of single CPU? BTW, writing the bit is done on the same CPU. If yes, this machine may not obey cache consistency, IMO.
Also smp_mb() is really barrier() in case of non-SMP, looks non-SMP code still works well without other barrier required even though with speculate loads.
Thanks,
Ming
Quoted 7 lines
Thanks,
Will
Signature · 1 line
Ming
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 47 lines · Ming Lei
Quoted 38 lines · Will Deacon
Quoted 21 lines · Ming Lei
Quoted 5 lines · Peter Zijlstra
Quoted 4 lines · Christoph Hellwig
block/blk-mq.c +0
-0atomic_inc (&data.hctx->nr_active); } data.hctx->tags->rqs[rq->tag] = rq;Quoted 12 lines
block/blk-mq.c static bool __blk_mq_get_driver_tag(struct request *rq) · line 1061
Quoted 9 lines
block/blk-mq.c +6
-0/* +* Ensure updates to rq->tag and tags->rqs[] are seen by +* blk_mq_tags_inflight_rqs. This pairs with the smp_mb__after_atomic +* in blk_mq_hctx_notify_offline. This only matters in case a process +* gets migrated to another CPU that is not mapped to this hctx. */ +if (rq->mq_ctx->cpu !=get_cpu ())smp_mb (); +put_cpu ();This looks exceedingly weird; how do you think you can get to another CPU and not have an
smp_mb()implied in the migration itself? Also, whatWhat we need is one
smp_mb()between the following two OPs:Quoted 8 lines
1)
rq->tag = rq->internal_tag; data.hctx->tags->rqs[rq->tag] = rq;2)
if (unlikely(test_bit(BLK_MQ_S_INACTIVE, &rq->mq_hctx->state)))And the pair of the above barrier is in
blk_mq_hctx_notify_offline().I'm struggling with this, so let me explain why. My understanding of the original patch [1] and your explanation above is that you want *either* of the following behaviours
-
__blk_mq_get_driver_tag()(i.e. (1) above) andtest_bit(BLK_MQ_S_INACTIVE, ...)run on the same CPU withbarrier()between them, orQuoted 7 lines
- There is a migration and therefore an implied
smp_mb()between themHowever, given that most CPUs can speculate loads (and therefore the
test_bit()operation), I don't understand how the "everything runs on the same CPU" is safe if abarrier()is required. In other words, if thebarrier()is needed to prevent the compiler hoisting the load, then the CPU can still cause problems.
Quoted 4 lines
Do you think the speculate loads may return wrong value of
BLK_MQ_S_INACTIVEbit in case of single CPU? BTW, writing the bit is done on the same CPU. If yes, this machine may not obey cache consistency, IMO.
If the write is on the same CPU, then the read will of course return the value written by that write, otherwise we'd have much bigger problems!
But then I'm confused, because you're saying that the write is done on the same CPU, but previously you were saying that migration occuring before (1) was problematic. Can you explain a bit more about that case, please? What is running before (1) that is relevant here?
Thanks,
Will
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 48 lines · Will Deacon
Quoted 47 lines · Ming Lei
Quoted 45 lines · Will Deacon
Quoted 21 lines · Ming Lei
Quoted 5 lines · Peter Zijlstra
Quoted 4 lines · Christoph Hellwig
block/blk-mq.c +0
-0atomic_inc (&data.hctx->nr_active); } data.hctx->tags->rqs[rq->tag] = rq;Quoted 12 lines
block/blk-mq.c static bool __blk_mq_get_driver_tag(struct request *rq) · line 1061
Quoted 9 lines
block/blk-mq.c +6
-0/* +* Ensure updates to rq->tag and tags->rqs[] are seen by +* blk_mq_tags_inflight_rqs. This pairs with the smp_mb__after_atomic +* in blk_mq_hctx_notify_offline. This only matters in case a process +* gets migrated to another CPU that is not mapped to this hctx. */ +if (rq->mq_ctx->cpu !=get_cpu ())smp_mb (); +put_cpu ();This looks exceedingly weird; how do you think you can get to another CPU and not have an
smp_mb()implied in the migration itself? Also, whatWhat we need is one
smp_mb()between the following two OPs:Quoted 8 lines
1)
rq->tag = rq->internal_tag; data.hctx->tags->rqs[rq->tag] = rq;2)
if (unlikely(test_bit(BLK_MQ_S_INACTIVE, &rq->mq_hctx->state)))And the pair of the above barrier is in
blk_mq_hctx_notify_offline().I'm struggling with this, so let me explain why. My understanding of the original patch [1] and your explanation above is that you want *either* of the following behaviours
-
__blk_mq_get_driver_tag()(i.e. (1) above) andtest_bit(BLK_MQ_S_INACTIVE, ...)run on the same CPU withbarrier()between them, or- There is a migration and therefore an implied
smp_mb()between themHowever, given that most CPUs can speculate loads (and therefore the
test_bit()operation), I don't understand how the "everything runs on the same CPU" is safe if abarrier()is required. In other words, if thebarrier()is needed to prevent the compiler hoisting the load, then the CPU can still cause problems.
Quoted 7 lines
Quoted 4 lines
Do you think the speculate loads may return wrong value of
BLK_MQ_S_INACTIVEbit in case of single CPU? BTW, writing the bit is done on the same CPU. If yes, this machine may not obey cache consistency, IMO.If the write is on the same CPU, then the read will of course return the value written by that write, otherwise we'd have much bigger problems!
OK, then it is nothing to with speculate loads.
Quoted 5 lines
But then I'm confused, because you're saying that the write is done on the same CPU, but previously you were saying that migration occuring before (1) was problematic. Can you explain a bit more about that case, please? What is running before (1) that is relevant here?
Please see the following two code paths:
[1] code path1:blk_mq_hctx_notify_offline():
set_bit(BLK_MQ_S_INACTIVE, &hctx->state); smp_mb() or smp_mb_after_atomic() blk_mq_hctx_drain_inflight_rqs(): blk_mq_tags_inflight_rqs() rq = hctx->tags->rqs[index] and READ rq->tag
[2] code path2:
blk_mq_get_driver_tag():
process might be migrated to other CPU here and chance is small, then the follow code will be run on CPU different with code path1
rq->tag = rq->internal_tag;
hctx->tags->rqs[rq->tag] = rq;
barrier() in case that code path2 is run on same CPU with code path1 OR
smp_mb() in case that code path2 is run on different CPU with code path1 because of process migration
test_bit(BLK_MQ_S_INACTIVE, &data.hctx->state)
Thanks,
Ming
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 79 lines · Ming Lei
Quoted 48 lines · Will Deacon
Quoted 47 lines · Ming Lei
Quoted 45 lines · Will Deacon
Quoted 21 lines · Ming Lei
Quoted 5 lines · Peter Zijlstra
Quoted 4 lines · Christoph Hellwig
(quoted diff) +0
-0atomic_inc(&data.hctx->nr_active); } data.hctx->tags->rqs[rq->tag] = rq;Quoted 12 lines
Review
Quoted 9 lines
(quoted diff) +6
-0/* + * Ensure updates to rq->tag and tags->rqs[] are seen by + * blk_mq_tags_inflight_rqs. This pairs with the smp_mb__after_atomic + * in blk_mq_hctx_notify_offline. This only matters in case a process + * gets migrated to another CPU that is not mapped to this hctx. */ + if (rq->mq_ctx->cpu != get_cpu()) smp_mb(); + put_cpu();This looks exceedingly weird; how do you think you can get to another CPU and not have an
smp_mb()implied in the migration itself? Also, whatWhat we need is one
smp_mb()between the following two OPs:Quoted 8 lines
1)
rq->tag = rq->internal_tag; data.hctx->tags->rqs[rq->tag] = rq;2)
if (unlikely(test_bit(BLK_MQ_S_INACTIVE, &rq->mq_hctx->state)))And the pair of the above barrier is in
blk_mq_hctx_notify_offline().I'm struggling with this, so let me explain why. My understanding of the original patch [1] and your explanation above is that you want *either* of the following behaviours
-
__blk_mq_get_driver_tag()(i.e. (1) above) andtest_bit(BLK_MQ_S_INACTIVE, ...)run on the same CPU withbarrier()between them, or- There is a migration and therefore an implied
smp_mb()between themHowever, given that most CPUs can speculate loads (and therefore the
test_bit()operation), I don't understand how the "everything runs on the same CPU" is safe if abarrier()is required. In other words, if thebarrier()is needed to prevent the compiler hoisting the load, then the CPU can still cause problems.Quoted 7 lines
Quoted 4 lines
Do you think the speculate loads may return wrong value of
BLK_MQ_S_INACTIVEbit in case of single CPU? BTW, writing the bit is done on the same CPU. If yes, this machine may not obey cache consistency, IMO.If the write is on the same CPU, then the read will of course return the value written by that write, otherwise we'd have much bigger problems!
OK, then it is nothing to with speculate loads.
Quoted 5 lines
But then I'm confused, because you're saying that the write is done on the same CPU, but previously you were saying that migration occuring before (1) was problematic. Can you explain a bit more about that case, please? What is running before (1) that is relevant here?
Please see the following two code paths:
[1] code path1:
blk_mq_hctx_notify_offline():set_bit(BLK_MQ_S_INACTIVE, &hctx->state); smp_mb() or smp_mb_after_atomic() blk_mq_hctx_drain_inflight_rqs(): blk_mq_tags_inflight_rqs() rq = hctx->tags->rqs[index] and READ rq->tag
Quoted 8 lines
[2] code path2:
blk_mq_get_driver_tag(): process might be migrated to other CPU here and chance is small, then the follow code will be run on CPU different with code path1 rq->tag = rq->internal_tag; hctx->tags->rqs[rq->tag] = rq;
I /think/ this can be distilled to the SB litmus test:
// blk_mq_hctx_notify_offline() blk_mq_get_driver_tag(); Wstate = INACTIVE Wtag smp_mb() smp_mb() Rtag Rstate
and you want to make sure that either blk_mq_get_driver_tag() sees the state as INACTIVE and does the cleanup, or it doesn't and blk_mq_hctx_notify_offline() sees the newly written tag and waits for the request to complete (I don't get how that happens, but hey).
Is that right?
Quoted 6 lines
barrier()in case that code path2 is run on same CPU with code path1 OR
smp_mb()in case that code path2 is run on different CPU with code path1 because of process migration
test_bit(BLK_MQ_S_INACTIVE, &data.hctx->state)
Couldn't you just check this at the start of blk_mq_get_driver_tag() as well, and then make the smp_mb() unconditional?
Will
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 96 lines · Will Deacon
Quoted 79 lines · Ming Lei
Quoted 48 lines · Will Deacon
Quoted 47 lines · Ming Lei
Quoted 45 lines · Will Deacon
Quoted 21 lines · Ming Lei
Quoted 5 lines · Peter Zijlstra
Quoted 4 lines · Christoph Hellwig
(quoted diff) +0
-0atomic_inc(&data.hctx->nr_active); } data.hctx->tags->rqs[rq->tag] = rq;Quoted 12 lines
Review
Quoted 9 lines
(quoted diff) +6
-0/* + * Ensure updates to rq->tag and tags->rqs[] are seen by + * blk_mq_tags_inflight_rqs. This pairs with the smp_mb__after_atomic + * in blk_mq_hctx_notify_offline. This only matters in case a process + * gets migrated to another CPU that is not mapped to this hctx. */ + if (rq->mq_ctx->cpu != get_cpu()) smp_mb(); + put_cpu();This looks exceedingly weird; how do you think you can get to another CPU and not have an
smp_mb()implied in the migration itself? Also, whatWhat we need is one
smp_mb()between the following two OPs:Quoted 8 lines
1)
rq->tag = rq->internal_tag; data.hctx->tags->rqs[rq->tag] = rq;2)
if (unlikely(test_bit(BLK_MQ_S_INACTIVE, &rq->mq_hctx->state)))And the pair of the above barrier is in
blk_mq_hctx_notify_offline().I'm struggling with this, so let me explain why. My understanding of the original patch [1] and your explanation above is that you want *either* of the following behaviours
-
__blk_mq_get_driver_tag()(i.e. (1) above) andtest_bit(BLK_MQ_S_INACTIVE, ...)run on the same CPU withbarrier()between them, or- There is a migration and therefore an implied
smp_mb()between themHowever, given that most CPUs can speculate loads (and therefore the
test_bit()operation), I don't understand how the "everything runs on the same CPU" is safe if abarrier()is required. In other words, if thebarrier()is needed to prevent the compiler hoisting the load, then the CPU can still cause problems.Quoted 7 lines
Quoted 4 lines
Do you think the speculate loads may return wrong value of
BLK_MQ_S_INACTIVEbit in case of single CPU? BTW, writing the bit is done on the same CPU. If yes, this machine may not obey cache consistency, IMO.If the write is on the same CPU, then the read will of course return the value written by that write, otherwise we'd have much bigger problems!
OK, then it is nothing to with speculate loads.
Quoted 5 lines
But then I'm confused, because you're saying that the write is done on the same CPU, but previously you were saying that migration occuring before (1) was problematic. Can you explain a bit more about that case, please? What is running before (1) that is relevant here?
Please see the following two code paths:
[1] code path1:
blk_mq_hctx_notify_offline():set_bit(BLK_MQ_S_INACTIVE, &hctx->state); smp_mb() or smp_mb_after_atomic() blk_mq_hctx_drain_inflight_rqs(): blk_mq_tags_inflight_rqs() rq = hctx->tags->rqs[index] and READ rq->tagQuoted 8 lines
[2] code path2:
blk_mq_get_driver_tag(): process might be migrated to other CPU here and chance is small, then the follow code will be run on CPU different with code path1 rq->tag = rq->internal_tag; hctx->tags->rqs[rq->tag] = rq;I /think/ this can be distilled to the SB litmus test:
// blk_mq_hctx_notify_offline() blk_mq_get_driver_tag(); Wstate = INACTIVE Wtag smp_mb() smp_mb() Rtag Rstate
Quoted 6 lines
and you want to make sure that either
blk_mq_get_driver_tag()sees the state as INACTIVE and does the cleanup, or it doesn't andblk_mq_hctx_notify_offline()sees the newly written tag and waits for the request to complete (I don't get how that happens, but hey).Is that right?
Yeah, exactly.
Quoted 10 lines
Quoted 7 lines
barrier()in case that code path2 is run on same CPU with code path1 OR
smp_mb()in case that code path2 is run on different CPU with code path1 because of process migration
test_bit(BLK_MQ_S_INACTIVE, &data.hctx->state)Couldn't you just check this at the start of
blk_mq_get_driver_tag()as well, and then make thesmp_mb()unconditional?
As I mentioned, the chance for the current process(calling blk_mq_get_driver_tag()) migration is very small, we do want to avoid the extra smp_mb() in the fast path.
Thanks,
Ming
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 47 lines · Ming Lei
Quoted 31 lines · Will Deacon
Quoted 14 lines · Ming Lei
Please see the following two code paths:
[1] code path1:
blk_mq_hctx_notify_offline():set_bit(BLK_MQ_S_INACTIVE, &hctx->state); smp_mb() or smp_mb_after_atomic() blk_mq_hctx_drain_inflight_rqs(): blk_mq_tags_inflight_rqs() rq = hctx->tags->rqs[index] and READ rq->tagQuoted 8 lines
[2] code path2:
blk_mq_get_driver_tag(): process might be migrated to other CPU here and chance is small, then the follow code will be run on CPU different with code path1 rq->tag = rq->internal_tag; hctx->tags->rqs[rq->tag] = rq;I /think/ this can be distilled to the SB litmus test:
// blk_mq_hctx_notify_offline() blk_mq_get_driver_tag(); Wstate = INACTIVE Wtag smp_mb() smp_mb() Rtag RstateQuoted 6 lines
and you want to make sure that either
blk_mq_get_driver_tag()sees the state as INACTIVE and does the cleanup, or it doesn't andblk_mq_hctx_notify_offline()sees the newly written tag and waits for the request to complete (I don't get how that happens, but hey).Is that right?
Yeah, exactly.
Quoted 6 lines
Quoted 6 lines
barrier()in case that code path2 is run on same CPU with code path1 OR
smp_mb()in case that code path2 is run on different CPU with code path1 because of process migration
Quoted 8 lines
Quoted 4 lines
Quoted 1 line
test_bit(BLK_MQ_S_INACTIVE, &data.hctx->state)Couldn't you just check this at the start of
blk_mq_get_driver_tag()as well, and then make thesmp_mb()unconditional?As I mentioned, the chance for the current
process(calling blk_mq_get_driver_tag())migration is very small, we do want to avoid the extrasmp_mb()in the fast path.
Hmm, but your suggestion of checking 'rq->mq_ctx->cpu' only works if that is the same CPU on which blk_mq_hctx_notify_offline() executes. What provides that guarantee?
If there's any chance of this thing being concurrent, then you need the barrier there just in case. So I'd say you either need to prevent the race, or live with the barrier. Do you have numbers to show how expensive it is?
Will
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 53 lines · Will Deacon
Quoted 52 lines · Ming Lei
Quoted 31 lines · Will Deacon
Quoted 14 lines · Ming Lei
Please see the following two code paths:
[1] code path1:
blk_mq_hctx_notify_offline():set_bit(BLK_MQ_S_INACTIVE, &hctx->state); smp_mb() or smp_mb_after_atomic() blk_mq_hctx_drain_inflight_rqs(): blk_mq_tags_inflight_rqs() rq = hctx->tags->rqs[index] and READ rq->tagQuoted 8 lines
[2] code path2:
blk_mq_get_driver_tag(): process might be migrated to other CPU here and chance is small, then the follow code will be run on CPU different with code path1 rq->tag = rq->internal_tag; hctx->tags->rqs[rq->tag] = rq;I /think/ this can be distilled to the SB litmus test:
// blk_mq_hctx_notify_offline() blk_mq_get_driver_tag(); Wstate = INACTIVE Wtag smp_mb() smp_mb() Rtag RstateQuoted 6 lines
and you want to make sure that either
blk_mq_get_driver_tag()sees the state as INACTIVE and does the cleanup, or it doesn't andblk_mq_hctx_notify_offline()sees the newly written tag and waits for the request to complete (I don't get how that happens, but hey).Is that right?
Yeah, exactly.
Quoted 10 lines
Quoted 7 lines
barrier()in case that code path2 is run on same CPU with code path1 OR
smp_mb()in case that code path2 is run on different CPU with code path1 because of process migration
test_bit(BLK_MQ_S_INACTIVE, &data.hctx->state)Couldn't you just check this at the start of
blk_mq_get_driver_tag()as well, and then make thesmp_mb()unconditional?
Quoted 7 lines
Quoted 3 lines
As I mentioned, the chance for the current
process(calling blk_mq_get_driver_tag())migration is very small, we do want to avoid the extrasmp_mb()in the fast path.Hmm, but your suggestion of checking '
rq->mq_ctx->cpu' only works if that is the same CPU on whichblk_mq_hctx_notify_offline()executes. What provides that guarantee?
BLK_MQ_S_INACTIVE is only set when the last cpu of this hctx is becoming offline, and blk_mq_hctx_notify_offline() is called from cpu hotplug handler. So if there is any request of this hctx submitted from somewhere, it has to this last cpu. That is done by blk-mq's queue mapping.
In case of direct issue, basically blk_mq_get_driver_tag() is run after the request is allocated, that is why I mentioned the chance of migration is very small.
Quoted 2 lines
If there's any chance of this thing being concurrent, then you need the
The only chance is that the process running blk_mq_get_driver_tag is migrated to another CPU in case of direct issue. And we do add smp_mb() for this case.
Quoted 2 lines
barrier there just in case. So I'd say you either need to prevent the race, or live with the barrier. Do you have numbers to show how expensive it is?
Not yet, but we can save it easily in the very fast path, so why not do it? Especially most of times preemption won't happen at all.
Also this patch itself is correct, and preempt disable via get_cpu() suggested by Christoph isn't needed too, because migration implies smp_mb(). I will document this point in next version.
Thanks,
Ming
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 8 lines · Ming Lei
BLK_MQ_S_INACTIVEis only set when the last cpu of this hctx is becoming offline, andblk_mq_hctx_notify_offline()is called from cpu hotplug handler. So if there is any request of this hctx submitted from somewhere, it has to this last cpu. That is done by blk-mq's queue mapping.In case of direct issue, basically
blk_mq_get_driver_tag()is run after the request is allocated, that is why I mentioned the chance of migration is very small.
"very small" does not cut it, it has to be zero. And it seems the new version still has this hack.
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 6 lines · Christoph Hellwig
Quoted 5 lines · Ming Lei
BLK_MQ_S_INACTIVEis only set when the last cpu of this hctx is becoming offline, andblk_mq_hctx_notify_offline()is called from cpu hotplug handler. So if there is any request of this hctx submitted from somewhere, it has to this last cpu. That is done by blk-mq's queue mapping.
Quoted 6 lines
Quoted 3 lines
In case of direct issue, basically
blk_mq_get_driver_tag()is run after the request is allocated, that is why I mentioned the chance of migration is very small."very small" does not cut it, it has to be zero. And it seems the new version still has this hack.
But smp_mb() is used for ordering the WRITE and READ, so it is correct.
barrier() is enough when process migration doesn't happen.
thank,
Ming
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 11 lines · Ming Lei
Quoted 10 lines · Christoph Hellwig
Quoted 8 lines · Ming Lei
BLK_MQ_S_INACTIVEis only set when the last cpu of this hctx is becoming offline, andblk_mq_hctx_notify_offline()is called from cpu hotplug handler. So if there is any request of this hctx submitted from somewhere, it has to this last cpu. That is done by blk-mq's queue mapping.In case of direct issue, basically
blk_mq_get_driver_tag()is run after the request is allocated, that is why I mentioned the chance of migration is very small.
Quoted 6 lines
Quoted 2 lines
"very small" does not cut it, it has to be zero. And it seems the new version still has this hack.
But
smp_mb()is used for ordering the WRITE and READ, so it is correct.
barrier()is enough when process migration doesn't happen.
Without numbers I would just make the smp_mb() unconditional. Your questionable optimisation trades that for a load of the CPU ID and a conditional branch, which isn't obviously faster to me. It's also very difficult to explain to people and relies on a bunch of implicit behaviour (e.g. racing only with CPU-affine hotplug notifier).
If it turns out that the smp_mb() is worthwhile, then I'd suggest improving the comment, perhaps to include the litmus test I cooked previously.
Will
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 15 lines · Will Deacon
Quoted 14 lines · Ming Lei
Quoted 12 lines · Christoph Hellwig
Quoted 8 lines · Ming Lei
BLK_MQ_S_INACTIVEis only set when the last cpu of this hctx is becoming offline, andblk_mq_hctx_notify_offline()is called from cpu hotplug handler. So if there is any request of this hctx submitted from somewhere, it has to this last cpu. That is done by blk-mq's queue mapping.In case of direct issue, basically
blk_mq_get_driver_tag()is run after the request is allocated, that is why I mentioned the chance of migration is very small."very small" does not cut it, it has to be zero. And it seems the new version still has this hack.
Quoted 7 lines
Quoted 3 lines
But
smp_mb()is used for ordering the WRITE and READ, so it is correct.
barrier()is enough when process migration doesn't happen.Without numbers I would just make the
smp_mb()unconditional. Your questionable optimisation trades that for a load of the CPU ID and a conditional branch, which isn't obviously faster to me. It's also very
The CPU ID is just percpu READ, and unlikely() has been used for optimizing the conditional branch. And smp_mb() could cause CPU stall, I guess, so it should be much slower than reading CPU ID.
Let's see the attached microbench[1], the result shows that smp_mb() is 10+ times slower than smp_processor_id() with one conditional branch.
[ 1.239951] test_foo: smp_mb 738701907 smp_id 62904315 result 0 overflow 5120
The micronbench is run on simple 8cores KVM guest, and cpu is
'Model name: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz'.
Result is pretty stable in my 5 runs of VM boot.
Quoted 2 lines
difficult to explain to people and relies on a bunch of implicit behaviour (e.g. racing only with CPU-affine hotplug notifier).
It can be documented easily.
Quoted 3 lines
If it turns out that the
smp_mb()is worthwhile, then I'd suggest improving the comment, perhaps to include the litmus test I cooked previously.
I have added big comment on this usage in V10 already.
[1] miscrobench
block/blk-mq.c +39 -0
@@ -3836,8 +3836,47 @@ unsigned int blk_mq_rq_cpu(struct request *rq) }EXPORT_SYMBOL (blk_mq_rq_cpu); +static unsigned long test_smp_mb (unsigned long cnt) +{ +unsigned long start =local_clock (); + +while (cnt--) +smp_mb (); + +return local_clock () - start; +} + +static unsigned long test_smp_id (unsigned long cnt,short *result,int *overflow) +{ +unsigned long start =local_clock (); + +while (cnt--) { +short cpu =smp_processor_id (); + *result += cpu; +if (unlikely (*result ==0 )) + (*overflow)++; + } +return local_clock () - start; +} + +static void test_foo (void ) +{ +const unsigned long cnt =10 <<24 ; +short result =0 ; +int overflow =0 ; +unsigned long v1, v2; + + v1 =test_smp_mb (cnt); + v2 =test_smp_id (cnt, &result, &overflow); + +printk ("%s: smp_mb %lu smp_id %lu result %d overflow %d\n" , + __func__, v1, v2, (int )result, overflow); +} +static int __init blk_mq_init (void ) { +test_foo (); +cpuhp_setup_state_multi (CPUHP_BLK_MQ_DEAD ,"block/mq:dead" ,NULL , blk_mq_hctx_notify_dead); cpuhp_setup_state_multi(CPUHP_AP_BLK_MQ_ONLINE, "block/mq:online",
Thanks,
Ming
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 20 lines · Ming Lei
Quoted 19 lines · Will Deacon
Quoted 17 lines · Ming Lei
Quoted 6 lines · Christoph Hellwig
Quoted 5 lines · Ming Lei
BLK_MQ_S_INACTIVEis only set when the last cpu of this hctx is becoming offline, andblk_mq_hctx_notify_offline()is called from cpu hotplug handler. So if there is any request of this hctx submitted from somewhere, it has to this last cpu. That is done by blk-mq's queue mapping.Quoted 6 lines
Quoted 3 lines
In case of direct issue, basically
blk_mq_get_driver_tag()is run after the request is allocated, that is why I mentioned the chance of migration is very small."very small" does not cut it, it has to be zero. And it seems the new version still has this hack.
But
smp_mb()is used for ordering the WRITE and READ, so it is correct.
barrier()is enough when process migration doesn't happen.
Quoted 7 lines
Quoted 3 lines
Without numbers I would just make the
smp_mb()unconditional. Your questionable optimisation trades that for a load of the CPU ID and a conditional branch, which isn't obviously faster to me. It's also veryThe CPU ID is just percpu READ, and
unlikely()has been used for optimizing the conditional branch. Andsmp_mb()could cause CPU stall, I guess, so it should be much slower than reading CPU ID.
Percpu accesses aren't uniformly cheap across architectures.
Quoted 2 lines
Let's see the attached microbench[1], the result shows that
smp_mb()is 10+ times slower thansmp_processor_id()with one conditional branch.
Nobody said anything about smp_mb() in a tight loop, so this is hardly surprising. Throughput of barrier instructions will hit a ceiling fairly quickly, but they don't have to cause stalls in general use. I would expect the numbers to converge if you added some back-off to the loops (e.g. ndelay() or something). But I was really hoping for some numbers from the block layer itself, since that's what we actually care about.
Quoted 6 lines
[ 1.239951] test_foo: smp_mb 738701907 smp_id 62904315 result 0 overflow 5120The micronbench is run on simple 8cores KVM guest, and cpu is
'Model name: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz'.Result is pretty stable in my 5 runs of VM boot.
Honestly, I get the impression that you're not particularly happy with me putting in the effort to review your patches, so I'll leave it up to Christoph as to whether he wants to predicate the concurrency design on a hokey microbenchmark.
FWIW: I agree that the code should work as you have it in v10, I just think it's unnecessarily complicated and fragile.
/me goes to review other things
Will
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 25 lines · Will Deacon
Quoted 24 lines · Ming Lei
Quoted 22 lines · Will Deacon
Quoted 11 lines · Ming Lei
Quoted 10 lines · Christoph Hellwig
Quoted 8 lines · Ming Lei
BLK_MQ_S_INACTIVEis only set when the last cpu of this hctx is becoming offline, andblk_mq_hctx_notify_offline()is called from cpu hotplug handler. So if there is any request of this hctx submitted from somewhere, it has to this last cpu. That is done by blk-mq's queue mapping.In case of direct issue, basically
blk_mq_get_driver_tag()is run after the request is allocated, that is why I mentioned the chance of migration is very small.Quoted 6 lines
Quoted 2 lines
"very small" does not cut it, it has to be zero. And it seems the new version still has this hack.
But
smp_mb()is used for ordering the WRITE and READ, so it is correct.
barrier()is enough when process migration doesn't happen.Without numbers I would just make the
smp_mb()unconditional. Your questionable optimisation trades that for a load of the CPU ID and a conditional branch, which isn't obviously faster to me. It's also very
Quoted 5 lines
Quoted 3 lines
The CPU ID is just percpu READ, and
unlikely()has been used for optimizing the conditional branch. Andsmp_mb()could cause CPU stall, I guess, so it should be much slower than reading CPU ID.Percpu accesses aren't uniformly cheap across architectures.
I believe percpu access is cheap enough than smp_mb() in almost every SMP ARCH, otherwise no one would use percpu variable on that ARCH.
Quoted 10 lines
Quoted 3 lines
Let's see the attached microbench[1], the result shows that
smp_mb()is 10+ times slower thansmp_processor_id()with one conditional branch.Nobody said anything about
smp_mb()in a tight loop, so this is hardly surprising. Throughput of barrier instructions will hit a ceiling fairly quickly, but they don't have to cause stalls in general use. I would expect the numbers to converge if you added some back-off to the loops (e.g.ndelay()or something). But I was really hoping for some numbers from the block layer itself, since that's what we actually care about.
I believe that the microbench is enough to show smp_mb() is much heavier and slower than smp_processor_id() with conditional branch.
Cause some aio or io uring workload just takes CPU to submit IO without any delay, and we don't want to take extra CPU unnecessarily in IO submission side. And IOPS may reach millions or dozens of millions level. Storage guys have been working very hard to optimize the whole IO path.
Quoted 8 lines
Quoted 7 lines
[ 1.239951] test_foo: smp_mb 738701907 smp_id 62904315 result 0 overflow 5120The micronbench is run on simple 8cores KVM guest, and cpu is
'Model name: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz'.Result is pretty stable in my 5 runs of VM boot.
Quoted 7 lines
Honestly, I get the impression that you're not particularly happy with me putting in the effort to review your patches, so I'll leave it up to Christoph as to whether he wants to predicate the concurrency design on a hokey microbenchmark.
FWIW: I agree that the code should work as you have it in v10, I just think it's unnecessarily complicated and fragile.
Yeah, it works and it is correct, and we can document the usage, another point is that CPU hotplug doesn't happen frequently, so we shouldn't introduce extra cost for handling cpu hotplug in fast IO path, meantime smp_mb() won't be something which can be ignored, especially in some big machine with lots of CPU cores.
Thanks,
Ming
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
In reply to Ming LeiQuoted 79 lines · Ming Lei
Quoted 48 lines · Will Deacon
Quoted 47 lines · Ming Lei
Quoted 45 lines · Will Deacon
Quoted 21 lines · Ming Lei
Quoted 5 lines · Peter Zijlstra
Quoted 4 lines · Christoph Hellwig
(quoted diff) +0
-0atomic_inc(&data.hctx->nr_active); } data.hctx->tags->rqs[rq->tag] = rq;Quoted 12 lines
Review
Quoted 9 lines
(quoted diff) +6
-0/* + * Ensure updates to rq->tag and tags->rqs[] are seen by + * blk_mq_tags_inflight_rqs. This pairs with the smp_mb__after_atomic + * in blk_mq_hctx_notify_offline. This only matters in case a process + * gets migrated to another CPU that is not mapped to this hctx. */ + if (rq->mq_ctx->cpu != get_cpu()) smp_mb(); + put_cpu();This looks exceedingly weird; how do you think you can get to another CPU and not have an
smp_mb()implied in the migration itself? Also, whatWhat we need is one
smp_mb()between the following two OPs:Quoted 8 lines
1)
rq->tag = rq->internal_tag; data.hctx->tags->rqs[rq->tag] = rq;2)
if (unlikely(test_bit(BLK_MQ_S_INACTIVE, &rq->mq_hctx->state)))And the pair of the above barrier is in
blk_mq_hctx_notify_offline().I'm struggling with this, so let me explain why. My understanding of the original patch [1] and your explanation above is that you want *either* of the following behaviours
-
__blk_mq_get_driver_tag()(i.e. (1) above) andtest_bit(BLK_MQ_S_INACTIVE, ...)run on the same CPU withbarrier()between them, or- There is a migration and therefore an implied
smp_mb()between themHowever, given that most CPUs can speculate loads (and therefore the
test_bit()operation), I don't understand how the "everything runs on the same CPU" is safe if abarrier()is required. In other words, if thebarrier()is needed to prevent the compiler hoisting the load, then the CPU can still cause problems.Quoted 7 lines
Quoted 4 lines
Do you think the speculate loads may return wrong value of
BLK_MQ_S_INACTIVEbit in case of single CPU? BTW, writing the bit is done on the same CPU. If yes, this machine may not obey cache consistency, IMO.If the write is on the same CPU, then the read will of course return the value written by that write, otherwise we'd have much bigger problems!
OK, then it is nothing to with speculate loads.
Quoted 5 lines
But then I'm confused, because you're saying that the write is done on the same CPU, but previously you were saying that migration occuring before (1) was problematic. Can you explain a bit more about that case, please? What is running before (1) that is relevant here?
Please see the following two code paths:
[1] code path1:
blk_mq_hctx_notify_offline():set_bit(BLK_MQ_S_INACTIVE, &hctx->state); smp_mb() or smp_mb_after_atomic() blk_mq_hctx_drain_inflight_rqs(): blk_mq_tags_inflight_rqs() rq = hctx->tags->rqs[index] and READ rq->tag
Quoted 5 lines
[2] code path2:
blk_mq_get_driver_tag():process might be migrated to other CPU here and chance is small, then the follow code will be run on CPU different with code path1
If the process is migrated from one CPU to another, each CPU will execute full barriers (smp_mb() or equivalent) as part of the migration. Do those barriers help prevent the undesired outcome?
Thanx, Paul
Quoted 15 lines
rq->tag = rq->internal_tag; hctx->tags->rqs[rq->tag] = rq; barrier() in case that code path2 is run on same CPU with code path1 OR smp_mb() in case that code path2 is run on different CPU with code path1 because of process migration test_bit(BLK_MQ_S_INACTIVE, &data.hctx->state)Thanks,
Ming
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 83 lines · Paul E. McKenney
Quoted 82 lines · Ming Lei
Quoted 48 lines · Will Deacon
Quoted 47 lines · Ming Lei
Quoted 45 lines · Will Deacon
Quoted 21 lines · Ming Lei
Quoted 5 lines · Peter Zijlstra
Quoted 4 lines · Christoph Hellwig
(quoted diff) +0
-0atomic_inc(&data.hctx->nr_active); } data.hctx->tags->rqs[rq->tag] = rq;Quoted 12 lines
Review
Quoted 9 lines
(quoted diff) +6
-0/* + * Ensure updates to rq->tag and tags->rqs[] are seen by + * blk_mq_tags_inflight_rqs. This pairs with the smp_mb__after_atomic + * in blk_mq_hctx_notify_offline. This only matters in case a process + * gets migrated to another CPU that is not mapped to this hctx. */ + if (rq->mq_ctx->cpu != get_cpu()) smp_mb(); + put_cpu();This looks exceedingly weird; how do you think you can get to another CPU and not have an
smp_mb()implied in the migration itself? Also, whatWhat we need is one
smp_mb()between the following two OPs:Quoted 8 lines
1)
rq->tag = rq->internal_tag; data.hctx->tags->rqs[rq->tag] = rq;2)
if (unlikely(test_bit(BLK_MQ_S_INACTIVE, &rq->mq_hctx->state)))And the pair of the above barrier is in
blk_mq_hctx_notify_offline().I'm struggling with this, so let me explain why. My understanding of the original patch [1] and your explanation above is that you want *either* of the following behaviours
-
__blk_mq_get_driver_tag()(i.e. (1) above) andtest_bit(BLK_MQ_S_INACTIVE, ...)run on the same CPU withbarrier()between them, or- There is a migration and therefore an implied
smp_mb()between themHowever, given that most CPUs can speculate loads (and therefore the
test_bit()operation), I don't understand how the "everything runs on the same CPU" is safe if abarrier()is required. In other words, if thebarrier()is needed to prevent the compiler hoisting the load, then the CPU can still cause problems.Quoted 7 lines
Quoted 4 lines
Do you think the speculate loads may return wrong value of
BLK_MQ_S_INACTIVEbit in case of single CPU? BTW, writing the bit is done on the same CPU. If yes, this machine may not obey cache consistency, IMO.If the write is on the same CPU, then the read will of course return the value written by that write, otherwise we'd have much bigger problems!
OK, then it is nothing to with speculate loads.
Quoted 5 lines
But then I'm confused, because you're saying that the write is done on the same CPU, but previously you were saying that migration occuring before (1) was problematic. Can you explain a bit more about that case, please? What is running before (1) that is relevant here?
Please see the following two code paths:
[1] code path1:
blk_mq_hctx_notify_offline():set_bit(BLK_MQ_S_INACTIVE, &hctx->state); smp_mb() or smp_mb_after_atomic() blk_mq_hctx_drain_inflight_rqs(): blk_mq_tags_inflight_rqs() rq = hctx->tags->rqs[index] and READ rq->tag[2] code path2:
blk_mq_get_driver_tag():
Quoted 6 lines
Quoted 2 lines
process might be migrated to other CPU here and chance is small, then the follow code will be run on CPU different with code path1
If the process is migrated from one CPU to another, each CPU will execute full barriers (
smp_mb()or equivalent) as part of the migration. Do those barriers help prevent the undesired outcome?
No, WRITE on rq->tag will be run on the new CPU which becomes different with another CPU on which READ rq->tag is done.
Thanks,
Ming
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
In reply to Ming LeiQuoted 155 lines · Ming Lei
Before one CPU becomes offline, check if it is the last online CPU of hctx. If yes, mark this hctx as inactive, meantime wait for completion of all in-flight IOs originated from this hctx. Meantime check if this hctx has become inactive in
blk_mq_get_driver_tag(), if yes, release the allocated tag.This way guarantees that there isn't any inflight IO before shutdowning the managed IRQ line when all CPUs of this IRQ line is offline.
Cc John Garry <[email protected]>Cc Bart Van Assche <[email protected]>Cc Hannes Reinecke <[email protected]>Cc Christoph Hellwig <[email protected]>Cc Thomas Gleixner <[email protected]>Signed-off-by Ming Lei <[email protected]>--- block/blk-mq-debugfs.c | 1 + block/blk-mq.c | 124 +++++++++++++++++++++++++++++++++++++---- include/linux/blk-mq.h | 3 + 3 files changed, 117 insertions(+), 11 deletions(-)block/blk-mq-debugfs.c +1
-0@@ -213,6 +213,7 @@ static const char *const hctx_state_name[] = {HCTX_STATE_NAME (STOPPED ),HCTX_STATE_NAME (TAG_ACTIVE ),HCTX_STATE_NAME (SCHED_RESTART ), + HCTX_STATE_NAME(INACTIVE), };#undef HCTX_STATE_NAMEblock/blk-mq.c +59
-9@@ -1050,11 +1050,31 @@ static bool __blk_mq_get_driver_tag(struct request *rq)return true; } -static bool blk_mq_get_driver_tag (struct request *rq) +static bool blk_mq_get_driver_tag (struct request *rq,bool direct_issue) {if (rq->tag !=-1 )return true; -return __blk_mq_get_driver_tag (rq); + +if (!__blk_mq_get_driver_tag (rq)) +return false; +/* +* Add one memory barrier in case that direct issue IO process is +* migrated to other CPU which may not belong to this hctx, so we can +* order driver tag assignment and checking BLK_MQ_S_INACTIVE. +* Otherwise, barrier() is enough given both setting BLK_MQ_S_INACTIVE +* and driver tag assignment are run on the same CPU in case that +* BLK_MQ_S_INACTIVE is set. +*/ +if (unlikely (direct_issue && rq->mq_ctx->cpu !=raw_smp_processor_id ())) +smp_mb (); +else +barrier (); + +if (unlikely (test_bit (BLK_MQ_S_INACTIVE , &rq->mq_hctx->state))) { +blk_mq_put_driver_tag (rq); +return false; + } +return true; } static int blk_mq_dispatch_wake(wait_queue_entry_t *wait, unsigned mode,@@ -1103,7 +1123,7 @@ static bool blk_mq_mark_tag_wait(struct blk_mq_hw_ctx *hctx,* Don't clear RESTART here, someone else could have set it. * At most this will cost an extra queue run. */ -return blk_mq_get_driver_tag (rq); +return blk_mq_get_driver_tag (rq, false); } wait = &hctx->dispatch_wait;@@ -1129,7 +1149,7 @@ static bool blk_mq_mark_tag_wait(struct blk_mq_hw_ctx *hctx,* allocation failure and adding the hardware queue to the wait * queue. */ - ret =blk_mq_get_driver_tag (rq); + ret =blk_mq_get_driver_tag (rq, false);if (!ret) {spin_unlock (&hctx->dispatch_wait_lock);spin_unlock_irq (&wq->lock);@@ -1228,7 +1248,7 @@ bool blk_mq_dispatch_rq_list(struct request_queue *q, struct list_head *list,break ; } -if (!blk_mq_get_driver_tag (rq)) { +if (!blk_mq_get_driver_tag (rq, false)) {/* * The initial allocation attempt failed, so we need to * rerun the hardware queue when a tag is freed. The @@ -1260,7 +1280,7 @@ bool blk_mq_dispatch_rq_list(struct request_queue *q, struct list_head *list, bd.last = true; else { nxt = list_first_entry(list, struct request, queuelist); - bd.last = !blk_mq_get_driver_tag (nxt); + bd.last = !blk_mq_get_driver_tag (nxt, false); } ret = q->mq_ops->queue_rq (hctx, &bd);@@ -1853,7 +1873,7 @@ static blk_status_t __blk_mq_try_issue_directly(struct blk_mq_hw_ctx *hctx,if (!blk_mq_get_dispatch_budget (hctx)) goto insert; -if (!blk_mq_get_driver_tag (rq)) { +if (!blk_mq_get_driver_tag (rq, true)) {blk_mq_put_dispatch_budget (hctx); goto insert; }@@ -2261,13 +2281,92 @@ int blk_mq_alloc_rqs(struct blk_mq_tag_set *set, struct blk_mq_tags *tags,return -ENOMEM ; } -static int blk_mq_hctx_notify_online (unsigned int cpu,struct hlist_node *node) +struct count_inflight_data { +unsigned count; +struct blk_mq_hw_ctx *hctx; +}; + +static bool blk_mq_count_inflight_rq (struct request *rq,void *data, +bool reserved) { -return 0 ; +struct count_inflight_data *count_data = data; + +/* +* Can't check rq's state because it is updated to MQ_RQ_IN_FLIGHT +* in blk_mq_start_request(), at that time we can't prevent this rq +* from being issued. +* +* So check if driver tag is assigned, if yes, count this rq as +* inflight. +*/ +if (rq->tag >=0 && rq->mq_hctx == count_data->hctx) + count_data->count++; + +return true; +} + +static bool blk_mq_inflight_rq (struct request *rq,void *data, +bool reserved) +{ +return rq->tag >=0 ; +} + +static unsigned blk_mq_tags_inflight_rqs (struct blk_mq_hw_ctx *hctx) +{ +struct count_inflight_data count_data = {
block/blk-mq.c int blk_mq_alloc_rqs(struct blk_mq_tag_set *set, struct blk_mq_tags *tags, · line 2326
Quoted 10 lines
block/blk-mq.c +10
-0+ .count = 0, + .hctx = hctx, + }; + +blk_mq_all_tag_busy_iter (hctx->tags, blk_mq_count_inflight_rq, + blk_mq_inflight_rq, &count_data); + +return count_data.count; +} +
Remind me again: Why do we need the 'filter' function here? Can't we just move the filter function into the main iterator and stay with the original implementation?
Quoted 70 lines
block/blk-mq.c +44
-2+static void blk_mq_hctx_drain_inflight_rqs (struct blk_mq_hw_ctx *hctx) +{ +while (1 ) { +if (!blk_mq_tags_inflight_rqs (hctx)) +break ; +msleep (5 ); + } }static int blk_mq_hctx_notify_offline (unsigned int cpu,struct hlist_node *node) { +struct blk_mq_hw_ctx *hctx =hlist_entry_safe (node, + struct blk_mq_hw_ctx, cpuhp_online); + +if (!cpumask_test_cpu (cpu, hctx->cpumask)) +return 0 ; + +if ((cpumask_next_and (-1 , hctx->cpumask, cpu_online_mask) != cpu) || + (cpumask_next_and (cpu, hctx->cpumask, cpu_online_mask) < nr_cpu_ids)) +return 0 ; + +/* +* The current CPU is the last one in this hctx, S_INACTIVE +* can be observed in dispatch path without any barrier needed, +* cause both are run on one same CPU. +*/ +set_bit (BLK_MQ_S_INACTIVE , &hctx->state); +/* +* Order setting BLK_MQ_S_INACTIVE and checking rq->tag & rqs[tag], +* and its pair is the smp_mb() in blk_mq_get_driver_tag +*/ +smp_mb__after_atomic (); +blk_mq_hctx_drain_inflight_rqs (hctx); +return 0 ; +} + +static int blk_mq_hctx_notify_online (unsigned int cpu,struct hlist_node *node) +{ +struct blk_mq_hw_ctx *hctx =hlist_entry_safe (node, + struct blk_mq_hw_ctx, cpuhp_online); + +if (cpumask_test_cpu (cpu, hctx->cpumask)) +clear_bit (BLK_MQ_S_INACTIVE , &hctx->state);return 0 ; }@@ -2278,12 +2377,15 @@ static int blk_mq_hctx_notify_offline(unsigned int cpu, struct hlist_node *node)*/ static int blk_mq_hctx_notify_dead (unsigned int cpu,struct hlist_node *node) { -struct blk_mq_hw_ctx *hctx; +struct blk_mq_hw_ctx *hctx =hlist_entry_safe (node, + struct blk_mq_hw_ctx, cpuhp_dead);struct blk_mq_ctx *ctx;LIST_HEAD (tmp);enum hctx_type type; - hctx = hlist_entry_safe(node, struct blk_mq_hw_ctx, cpuhp_dead); +if (!cpumask_test_cpu (cpu, hctx->cpumask)) +return 0 ; + ctx =__blk_mq_get_ctx (hctx->queue, cpu); type = hctx->type;include/linux/blk-mq.h +0
-0
include/linux/blk-mq.h enum { · line 411
Quoted 9 lines
include/linux/blk-mq.h +3
-0@@ -403,6 +403,9 @@ enum {BLK_MQ_S_TAG_ACTIVE =1 ,BLK_MQ_S_SCHED_RESTART =2 , +/* hw queue is inactive after all its CPUs become offline */ +BLK_MQ_S_INACTIVE =3 , +BLK_MQ_MAX_DEPTH =10240 , BLK_MQ_CPU_WORK_BATCH = 8,
Otherwise this looks good, and is exactly what we need. Thanks for doing the work!
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke Teamlead Storage & Networking [email protected] +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 154 lines · Hannes Reinecke
Quoted 153 lines · Ming Lei
Before one CPU becomes offline, check if it is the last online CPU of hctx. If yes, mark this hctx as inactive, meantime wait for completion of all in-flight IOs originated from this hctx. Meantime check if this hctx has become inactive in
blk_mq_get_driver_tag(), if yes, release the allocated tag.This way guarantees that there isn't any inflight IO before shutdowning the managed IRQ line when all CPUs of this IRQ line is offline.
Cc John Garry <[email protected]>Cc Bart Van Assche <[email protected]>Cc Hannes Reinecke <[email protected]>Cc Christoph Hellwig <[email protected]>Cc Thomas Gleixner <[email protected]>Signed-off-by Ming Lei <[email protected]>--- block/blk-mq-debugfs.c | 1 + block/blk-mq.c | 124 +++++++++++++++++++++++++++++++++++++---- include/linux/blk-mq.h | 3 + 3 files changed, 117 insertions(+), 11 deletions(-)block/blk-mq-debugfs.c +1
-0@@ -213,6 +213,7 @@ static const char *const hctx_state_name[] = {HCTX_STATE_NAME (STOPPED ),HCTX_STATE_NAME (TAG_ACTIVE ),HCTX_STATE_NAME (SCHED_RESTART ), + HCTX_STATE_NAME(INACTIVE), };#undef HCTX_STATE_NAMEblock/blk-mq.c +65
-9@@ -1050,11 +1050,31 @@ static bool __blk_mq_get_driver_tag(struct request *rq)return true; } -static bool blk_mq_get_driver_tag (struct request *rq) +static bool blk_mq_get_driver_tag (struct request *rq,bool direct_issue) {if (rq->tag !=-1 )return true; -return __blk_mq_get_driver_tag (rq); + +if (!__blk_mq_get_driver_tag (rq)) +return false; +/* +* Add one memory barrier in case that direct issue IO process is +* migrated to other CPU which may not belong to this hctx, so we can +* order driver tag assignment and checking BLK_MQ_S_INACTIVE. +* Otherwise, barrier() is enough given both setting BLK_MQ_S_INACTIVE +* and driver tag assignment are run on the same CPU in case that +* BLK_MQ_S_INACTIVE is set. +*/ +if (unlikely (direct_issue && rq->mq_ctx->cpu !=raw_smp_processor_id ())) +smp_mb (); +else +barrier (); + +if (unlikely (test_bit (BLK_MQ_S_INACTIVE , &rq->mq_hctx->state))) { +blk_mq_put_driver_tag (rq); +return false; + } +return true; } static int blk_mq_dispatch_wake(wait_queue_entry_t *wait, unsigned mode,@@ -1103,7 +1123,7 @@ static bool blk_mq_mark_tag_wait(struct blk_mq_hw_ctx *hctx,* Don't clear RESTART here, someone else could have set it. * At most this will cost an extra queue run. */ -return blk_mq_get_driver_tag (rq); +return blk_mq_get_driver_tag (rq, false); } wait = &hctx->dispatch_wait;@@ -1129,7 +1149,7 @@ static bool blk_mq_mark_tag_wait(struct blk_mq_hw_ctx *hctx,* allocation failure and adding the hardware queue to the wait * queue. */ - ret =blk_mq_get_driver_tag (rq); + ret =blk_mq_get_driver_tag (rq, false);if (!ret) {spin_unlock (&hctx->dispatch_wait_lock);spin_unlock_irq (&wq->lock);@@ -1228,7 +1248,7 @@ bool blk_mq_dispatch_rq_list(struct request_queue *q, struct list_head *list,break ; } -if (!blk_mq_get_driver_tag (rq)) { +if (!blk_mq_get_driver_tag (rq, false)) {/* * The initial allocation attempt failed, so we need to * rerun the hardware queue when a tag is freed. The @@ -1260,7 +1280,7 @@ bool blk_mq_dispatch_rq_list(struct request_queue *q, struct list_head *list, bd.last = true; else { nxt = list_first_entry(list, struct request, queuelist); - bd.last = !blk_mq_get_driver_tag (nxt); + bd.last = !blk_mq_get_driver_tag (nxt, false); } ret = q->mq_ops->queue_rq (hctx, &bd);@@ -1853,7 +1873,7 @@ static blk_status_t __blk_mq_try_issue_directly(struct blk_mq_hw_ctx *hctx,if (!blk_mq_get_dispatch_budget (hctx)) goto insert; -if (!blk_mq_get_driver_tag (rq)) { +if (!blk_mq_get_driver_tag (rq, true)) {blk_mq_put_dispatch_budget (hctx); goto insert; }@@ -2261,13 +2281,92 @@ int blk_mq_alloc_rqs(struct blk_mq_tag_set *set, struct blk_mq_tags *tags,return -ENOMEM ; } -static int blk_mq_hctx_notify_online (unsigned int cpu,struct hlist_node *node) +struct count_inflight_data { +unsigned count; +struct blk_mq_hw_ctx *hctx; +}; + +static bool blk_mq_count_inflight_rq (struct request *rq,void *data, +bool reserved) { -return 0 ; +struct count_inflight_data *count_data = data; + +/* +* Can't check rq's state because it is updated to MQ_RQ_IN_FLIGHT +* in blk_mq_start_request(), at that time we can't prevent this rq +* from being issued. +* +* So check if driver tag is assigned, if yes, count this rq as +* inflight. +*/ +if (rq->tag >=0 && rq->mq_hctx == count_data->hctx) + count_data->count++; + +return true; +} + +static bool blk_mq_inflight_rq (struct request *rq,void *data, +bool reserved) +{ +return rq->tag >=0 ; +} + +static unsigned blk_mq_tags_inflight_rqs (struct blk_mq_hw_ctx *hctx) +{ +struct count_inflight_data count_data = { + .count =0 , + .hctx = hctx, + }; + +blk_mq_all_tag_busy_iter (hctx->tags, blk_mq_count_inflight_rq, + blk_mq_inflight_rq, &count_data);
Quoted 8 lines
block/blk-mq.c int blk_mq_alloc_rqs(struct blk_mq_tag_set *set, struct blk_mq_tags *tags, · line 2326
Quoted 4 lines
block/blk-mq.c +4
-0+ +return count_data.count; +} +Remind me again: Why do we need the 'filter' function here? Can't we just move the filter function into the main iterator and stay with the original implementation?
This is a good question, cause it takes John and me days for figuring out reason of one IO hang.
The main iterator only iterates requests which blk_mq_request_started() returns true, see bt_tags_iter().
However, we prevent rq from being allocated a driver tag in blk_mq_get_driver_tag(). There is still some distance between assigning driver tag and calling into blk_mq_start_request() which is called from .queue_rq().
More importantly we can check nothing in blk_mq_start_request().
Thanks,
Ming
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
In reply to Ming Leiblock/blk-mq.c int blk_mq_alloc_rqs(struct blk_mq_tag_set *set, struct blk_mq_tags *tags, · line 2346
Quoted 11 lines · Ming Lei
static int
blk_mq_hctx_notify_offline(unsigned int cpu, struct hlist_node *node){block/blk-mq.c +9
-0+struct blk_mq_hw_ctx *hctx =hlist_entry_safe (node, + struct blk_mq_hw_ctx, cpuhp_online); + +if (!cpumask_test_cpu (cpu, hctx->cpumask)) +return 0 ; + +if ((cpumask_next_and (-1 , hctx->cpumask, cpu_online_mask) != cpu) || + (cpumask_next_and (cpu, hctx->cpumask, cpu_online_mask) < nr_cpu_ids)) +return 0 ;
nit: personally I prefer what we had previously, as it was easier to read, even if it did cause the code to be indented:
if ((cpumask_next_and(-1, cpumask, online_mask) == cpu) &&
(cpumask_next_and(cpu, cpumask, online_mask) >= nr_cpu_ids)) {
// do deactivate
}
return 0 and it could avoid the cpumask_test_cpu() test, unless you want that as an optimisation. If so, a comment could help.
cheers,
John
Quoted 16 lines
block/blk-mq.c +16
-0+ +/* +* The current CPU is the last one in this hctx, S_INACTIVE +* can be observed in dispatch path without any barrier needed, +* cause both are run on one same CPU. +*/ +set_bit (BLK_MQ_S_INACTIVE , &hctx->state); +/* +* Order setting BLK_MQ_S_INACTIVE and checking rq->tag & rqs[tag], +* and its pair is the smp_mb() in blk_mq_get_driver_tag +*/ +smp_mb__after_atomic (); +blk_mq_hctx_drain_inflight_rqs (hctx); +return 0 ; +} +
Re: [PATCH V8 07/11] blk-mq: stop to handle IO and drain IO before hctx becomes inactive
Quoted 17 lines · John Garry
block/blk-mq.c int blk_mq_alloc_rqs(struct blk_mq_tag_set *set, struct blk_mq_tags *tags, · line 2346
Quoted 11 lines · Ming Lei
static int
blk_mq_hctx_notify_offline(unsigned int cpu, struct hlist_node *node){block/blk-mq.c +9
-0+struct blk_mq_hw_ctx *hctx =hlist_entry_safe (node, + struct blk_mq_hw_ctx, cpuhp_online); + +if (!cpumask_test_cpu (cpu, hctx->cpumask)) +return 0 ; + +if ((cpumask_next_and (-1 , hctx->cpumask, cpu_online_mask) != cpu) || + (cpumask_next_and (cpu, hctx->cpumask, cpu_online_mask) < nr_cpu_ids)) +return 0 ;nit: personally I prefer what we had previously, as it was easier to read, even if it did cause the code to be indented:
Quoted 4 lines
if ((cpumask_next_and(-1, cpumask, online_mask) == cpu) &&
(cpumask_next_and(cpu, cpumask, online_mask) >= nr_cpu_ids)) {
// do deactivate
}I will document what the check does, given it can save us one level of indentation.
Quoted 5 lines
return 0
and it could avoid the
cpumask_test_cpu()test, unless you want that as an optimisation. If so, a comment could help.
cpumask_test_cpu() is more readable, and should be pattern for doing this stuff in cpuhp handler, cause the handler is called for any CPU to be offline.
Thanks,
Ming
PATCH v8 8/11 block: add blk_end_flush_machinery
In reply to Ming LeiFlush requests aren't same with normal FS request:
1) one dedicated per-hctx flush rq is pre-allocated for sending flush request
2) flush request si issued to hardware via one machinary so that flush merge can be applied
We can't simply re-submit flush rqs via blk_steal_bios(), so add blk_end_flush_machinery to collect flush requests which needs to be resubmitted:
- if one flush command without DATA is enough, send one flush, complete this kind of requests
- otherwise, add the request into a list and let caller re-submit it.
--- block/blk-flush.c | 123 +++++++++++++++++++++++++++++++++++++++++++--- block/blk.h | 4 ++ 2 files changed, 120 insertions(+), 7 deletions(-)
block/blk-flush.c +116 -7
@@ -170,10 +170,11 @@ static void blk_flush_complete_seq(struct request *rq,unsigned int cmd_flags;BUG_ON (rq->flush.seq & seq); - rq->flush.seq |= seq; +if (!error) + rq->flush.seq |= seq; cmd_flags = rq->cmd_flags; -if (likely (!error)) +if (likely (!error && !fq->flush_queue_terminating)) seq =blk_flush_cur_seq (rq);else seq =REQ_FSEQ_DONE ;
@@ -200,9 +201,15 @@ static void blk_flush_complete_seq(struct request *rq,* normal completion and end it. */ BUG_ON (!list_empty (&rq->queuelist)); -list_del_init (&rq->flush.list); -blk_flush_restore_request (rq); -blk_mq_end_request (rq, error); + +/* Terminating code will end the request from flush queue */ +if (likely (!fq->flush_queue_terminating)) { +list_del_init (&rq->flush.list); +blk_flush_restore_request (rq); +blk_mq_end_request (rq, error); + }else { +list_move_tail (&rq->flush.list, pending); + }break ;default :
@@ -279,7 +286,8 @@ static void blk_kick_flush(struct request_queue *q, struct blk_flush_queue *fq,struct request *flush_rq = fq->flush_rq;/* C1 described at the top of this file */ -if (fq->flush_pending_idx != fq->flush_running_idx ||list_empty (pending)) +if (fq->flush_pending_idx != fq->flush_running_idx || +list_empty (pending) || fq->flush_queue_terminating)return ;/* C2 and C3
@@ -331,7 +339,7 @@ static void mq_flush_data_end_io(struct request *rq, blk_status_t error)struct blk_flush_queue *fq =blk_get_flush_queue (q, ctx);if (q->elevator) { -WARN_ON (rq->tag <0 ); +WARN_ON (rq->tag <0 && !fq->flush_queue_terminating);blk_mq_put_driver_tag (rq); }
@@ -503,3 +511,104 @@ void blk_free_flush_queue(struct blk_flush_queue *fq)kfree (fq->flush_rq);kfree (fq); } + +static void __blk_end_queued_flush (struct blk_flush_queue *fq, +unsigned int queue_idx,struct list_head *resubmit_list, +struct list_head *flush_list) +{ +struct list_head *queue = &fq->flush_queue[queue_idx]; +struct request *rq, *nxt; + +list_for_each_entry_safe (rq, nxt, queue, flush.list) { +unsigned int seq =blk_flush_cur_seq (rq); + +list_del_init (&rq->flush.list); +blk_flush_restore_request (rq); +if (!blk_rq_sectors (rq) || seq ==REQ_FSEQ_POSTFLUSH ) +list_add_tail (&rq->queuelist, flush_list); +else +list_add_tail (&rq->queuelist, resubmit_list); + } +} + +static void blk_end_queued_flush (struct blk_flush_queue *fq, +struct list_head *resubmit_list,struct list_head *flush_list) +{ +unsigned long flags; + +spin_lock_irqsave (&fq->mq_flush_lock, flags); +__blk_end_queued_flush (fq,0 , resubmit_list, flush_list); +__blk_end_queued_flush (fq,1 , resubmit_list, flush_list); +spin_unlock_irqrestore (&fq->mq_flush_lock, flags); +} + +/* complete requests which just requires one flush command */ +static void blk_complete_flush_requests (struct blk_flush_queue *fq, +struct list_head *flush_list) +{ +struct block_device *bdev; +struct request *rq; +int error = -ENXIO ; + +if (list_empty (flush_list)) +return ; + + rq = list_first_entry(flush_list, struct request, queuelist); + +/* Send flush via one active hctx so we can move on */ + bdev =bdget_disk (rq->rq_disk,0 ); +if (bdev) { + error =blkdev_issue_flush (bdev,GFP_KERNEL ,NULL ); +bdput (bdev); + } + +while (!list_empty (flush_list)) { + rq = list_first_entry(flush_list, struct request, queuelist); +list_del_init (&rq->queuelist); +blk_mq_end_request (rq, error); + } +} + +/* +* Called when this hctx is inactive and all CPUs of this hctx is dead, +* otherwise don't reuse this function. +* +* Terminate this hw queue's flush machinery, and try to complete flush +* IO requests if possible, such as any flush IO without data, or flush +* data IO in POSTFLUSH stage. Otherwise, add the flush IOs into @list +* and let caller to re-submit them. +*/ +void blk_end_flush_machinery (struct blk_mq_hw_ctx *hctx, +struct list_head *in,struct list_head *out) +{ +LIST_HEAD (resubmit_list); +LIST_HEAD (flush_list); +struct blk_flush_queue *fq = hctx->fq; +struct request *rq, *nxt; +unsigned long flags; + +spin_lock_irqsave (&fq->mq_flush_lock, flags); + fq->flush_queue_terminating =1 ; +spin_unlock_irqrestore (&fq->mq_flush_lock, flags); + +/* End inflight flush requests */ +list_for_each_entry_safe (rq, nxt, in, queuelist) { +WARN_ON (!(rq->rq_flags &RQF_FLUSH_SEQ )); +list_del_init (&rq->queuelist); + rq->end_io (rq,BLK_STS_AGAIN ); + } + +/* End queued requests */ +blk_end_queued_flush (fq, &resubmit_list, &flush_list); + +/* Send flush and complete requests which just need one flush req */ +blk_complete_flush_requests (fq, &flush_list); + +spin_lock_irqsave (&fq->mq_flush_lock, flags); +/* reset flush queue so that it is ready to work next time */ + fq->flush_pending_idx = fq->flush_running_idx =0 ; + fq->flush_queue_terminating =0 ; +spin_unlock_irqrestore (&fq->mq_flush_lock, flags); + +list_splice_init (&resubmit_list, out); +}
block/blk.h +4 -0
@@ -20,6 +20,7 @@ struct blk_flush_queue { unsigned int flush_queue_delayed:1; unsigned int flush_pending_idx:1; unsigned int flush_running_idx:1; + unsigned int flush_queue_terminating:1;blk_status_t rq_status;unsigned long flush_pending_since;struct list_head flush_queue[2 ];
@@ -485,4 +486,7 @@ int __bio_add_pc_page(struct request_queue *q, struct bio *bio, struct page *page, unsigned int len, unsigned int offset, bool *same_page); +void blk_end_flush_machinery (struct blk_mq_hw_ctx *hctx, +struct list_head *in,struct list_head *out); +#endif /* BLK_INTERNAL_H */
Signature · 1 line
2.25.2
Re: [PATCH V8 08/11] block: add blk_end_flush_machinery
Quoted 9 lines · Ming Lei
block/blk-flush.c +9
-0+/* complete requests which just requires one flush command */ +static void blk_complete_flush_requests (struct blk_flush_queue *fq, +struct list_head *flush_list) +{ +struct block_device *bdev; +struct request *rq; +int error = -ENXIO ; + +if (list_empty (flush_list))
block/blk-flush.c void blk_free_flush_queue(struct blk_flush_queue *fq) · line 563
Quoted 10 lines
block/blk-flush.c +10
-0+return ; + + rq = list_first_entry(flush_list, struct request, queuelist); + +/* Send flush via one active hctx so we can move on */ + bdev =bdget_disk (rq->rq_disk,0 ); +if (bdev) { + error =blkdev_issue_flush (bdev,GFP_KERNEL ,NULL ); +bdput (bdev); + }
FYI, we don't really need the bdev to send a bio anymore, this could just do:
bio = bio_alloc(GFP_KERNEL, 0); // XXX: shouldn't this be GFP_NOIO?? bio->bi_disk = rq->rq_disk; bio->bi_partno = 0; bio_associate_blkg(bio); // XXX: actually, shouldn't this come from rq? bio->bi_opf = REQ_OP_WRITE | REQ_PREFLUSH; error = submit_bio_wait(bio); bio_put(bio);
Re: [PATCH V8 08/11] block: add blk_end_flush_machinery
Quoted 24 lines · Christoph Hellwig
Quoted 9 lines · Ming Lei
block/blk-flush.c +9
-0+/* complete requests which just requires one flush command */ +static void blk_complete_flush_requests (struct blk_flush_queue *fq, +struct list_head *flush_list) +{ +struct block_device *bdev; +struct request *rq; +int error = -ENXIO ; + +if (list_empty (flush_list))block/blk-flush.c void blk_free_flush_queue(struct blk_flush_queue *fq) · line 563
Quoted 10 lines
block/blk-flush.c +10
-0+return ; + + rq = list_first_entry(flush_list, struct request, queuelist); + +/* Send flush via one active hctx so we can move on */ + bdev =bdget_disk (rq->rq_disk,0 ); +if (bdev) { + error =blkdev_issue_flush (bdev,GFP_KERNEL ,NULL ); +bdput (bdev); + }FYI, we don't really need the bdev to send a bio anymore, this could just do:
Quoted 1 line
bio =
bio_alloc(GFP_KERNEL, 0); // XXX: shouldn't this beGFP_NOIO??
Error handling.
Quoted 6 lines
bio->bi_disk = rq->rq_disk; bio->bi_partno = 0; bio_associate_blkg(bio); // XXX: actually, shouldn't this come from rq? bio->bi_opf = REQ_OP_WRITE | REQ_PREFLUSH; error = submit_bio_wait(bio); bio_put(bio);
Yeah, that is another way, however I prefer to blkdev_issue_flush because it takes less code and we do have the API of blkdev_issue_flush.
Thanks,
Ming
Re: [PATCH V8 08/11] block: add blk_end_flush_machinery
Quoted 6 lines · Ming Lei
Quoted 4 lines
FYI, we don't really need the bdev to send a bio anymore, this could just do:
bio =
bio_alloc(GFP_KERNEL, 0); // XXX: shouldn't this beGFP_NOIO??Error handling.
bio_alloc does not fail for allocations that can sleep.
Quoted 10 lines
Quoted 7 lines
bio->bi_disk = rq->rq_disk; bio->bi_partno = 0; bio_associate_blkg(bio); // XXX: actually, shouldn't this come from rq? bio->bi_opf = REQ_OP_WRITE | REQ_PREFLUSH; error = submit_bio_wait(bio); bio_put(bio);Yeah, that is another way, however I prefer to
blkdev_issue_flushbecause it takes less code and we do have the API ofblkdev_issue_flush.
It is about the same amount of code, and as commented above I think the current code uses the wrong blkg assignment.
Re: [PATCH V8 08/11] block: add blk_end_flush_machinery
Quoted 18 lines · Christoph Hellwig
Quoted 6 lines · Ming Lei
Quoted 4 lines
FYI, we don't really need the bdev to send a bio anymore, this could just do:
bio =
bio_alloc(GFP_KERNEL, 0); // XXX: shouldn't this beGFP_NOIO??Error handling.
bio_allocdoes not fail for allocations that can sleep.Quoted 8 lines
Quoted 7 lines
bio->bi_disk = rq->rq_disk; bio->bi_partno = 0; bio_associate_blkg(bio); // XXX: actually, shouldn't this come from rq? bio->bi_opf = REQ_OP_WRITE | REQ_PREFLUSH; error = submit_bio_wait(bio); bio_put(bio);
Quoted 5 lines
Quoted 2 lines
Yeah, that is another way, however I prefer to
blkdev_issue_flushbecause it takes less code and we do have the API ofblkdev_issue_flush.It is about the same amount of code, and as commented above I think the current code uses the wrong blkg assignment.
There can be lots of flush requests which reply on this single flush emulation, then there can be more associated blkgs, so not sure we can select a correct one. But this single flush emulation is only triggered in very unlikey case, does it really matter to select one 'correct' blkcg for this single flush request without DATA?
BTW, block/blk-flush.c does run aggressive flush merge by the built-in per-hctx flush request and double queues, and blkcg can't account actual flush request accurately.
Thanks,
Ming
Re: [PATCH V8 08/11] block: add blk_end_flush_machinery
In reply to Ming LeiQuoted 136 lines · Ming Lei
Flush requests aren't same with normal FS request:
1) one dedicated per-hctx flush rq is pre-allocated for sending flush request
2) flush request si issued to hardware via one machinary so that flush merge can be applied
We can't simply re-submit flush rqs via
blk_steal_bios(), so addblk_end_flush_machineryto collect flush requests which needs to be resubmitted:- if one flush command without DATA is enough, send one flush, complete this kind of requests
- otherwise, add the request into a list and let caller re-submit it.
Cc John Garry <[email protected]>Cc Bart Van Assche <[email protected]>Cc Hannes Reinecke <[email protected]>Cc Christoph Hellwig <[email protected]>Cc Thomas Gleixner <[email protected]>Reviewed-by Christoph Hellwig <[email protected]>Signed-off-by Ming Lei <[email protected]>--- block/blk-flush.c | 123 +++++++++++++++++++++++++++++++++++++++++++--- block/blk.h | 4 ++ 2 files changed, 120 insertions(+), 7 deletions(-)block/blk-flush.c +63
-7@@ -170,10 +170,11 @@ static void blk_flush_complete_seq(struct request *rq,unsigned int cmd_flags;BUG_ON (rq->flush.seq & seq); - rq->flush.seq |= seq; +if (!error) + rq->flush.seq |= seq; cmd_flags = rq->cmd_flags; -if (likely (!error)) +if (likely (!error && !fq->flush_queue_terminating)) seq =blk_flush_cur_seq (rq);else seq =REQ_FSEQ_DONE ;@@ -200,9 +201,15 @@ static void blk_flush_complete_seq(struct request *rq,* normal completion and end it. */ BUG_ON (!list_empty (&rq->queuelist)); -list_del_init (&rq->flush.list); -blk_flush_restore_request (rq); -blk_mq_end_request (rq, error); + +/* Terminating code will end the request from flush queue */ +if (likely (!fq->flush_queue_terminating)) { +list_del_init (&rq->flush.list); +blk_flush_restore_request (rq); +blk_mq_end_request (rq, error); + }else { +list_move_tail (&rq->flush.list, pending); + }break ;default :@@ -279,7 +286,8 @@ static void blk_kick_flush(struct request_queue *q, struct blk_flush_queue *fq,struct request *flush_rq = fq->flush_rq;/* C1 described at the top of this file */ -if (fq->flush_pending_idx != fq->flush_running_idx ||list_empty (pending)) +if (fq->flush_pending_idx != fq->flush_running_idx || +list_empty (pending) || fq->flush_queue_terminating)return ;/* C2 and C3 @@ -331,7 +339,7 @@ static void mq_flush_data_end_io(struct request *rq, blk_status_t error)struct blk_flush_queue *fq =blk_get_flush_queue (q, ctx);if (q->elevator) { -WARN_ON (rq->tag <0 ); +WARN_ON (rq->tag <0 && !fq->flush_queue_terminating);blk_mq_put_driver_tag (rq); }@@ -503,3 +511,104 @@ void blk_free_flush_queue(struct blk_flush_queue *fq)kfree (fq->flush_rq);kfree (fq); } + +static void __blk_end_queued_flush (struct blk_flush_queue *fq, +unsigned int queue_idx,struct list_head *resubmit_list, +struct list_head *flush_list) +{ +struct list_head *queue = &fq->flush_queue[queue_idx]; +struct request *rq, *nxt; + +list_for_each_entry_safe (rq, nxt, queue, flush.list) { +unsigned int seq =blk_flush_cur_seq (rq); + +list_del_init (&rq->flush.list); +blk_flush_restore_request (rq); +if (!blk_rq_sectors (rq) || seq ==REQ_FSEQ_POSTFLUSH ) +list_add_tail (&rq->queuelist, flush_list); +else +list_add_tail (&rq->queuelist, resubmit_list); + } +} + +static void blk_end_queued_flush (struct blk_flush_queue *fq, +struct list_head *resubmit_list,struct list_head *flush_list) +{ +unsigned long flags; + +spin_lock_irqsave (&fq->mq_flush_lock, flags); +__blk_end_queued_flush (fq,0 , resubmit_list, flush_list); +__blk_end_queued_flush (fq,1 , resubmit_list, flush_list); +spin_unlock_irqrestore (&fq->mq_flush_lock, flags); +} + +/* complete requests which just requires one flush command */ +static void blk_complete_flush_requests (struct blk_flush_queue *fq, +struct list_head *flush_list) +{ +struct block_device *bdev; +struct request *rq; +int error = -ENXIO ; + +if (list_empty (flush_list)) +return ; + + rq = list_first_entry(flush_list, struct request, queuelist); + +/* Send flush via one active hctx so we can move on */ + bdev =bdget_disk (rq->rq_disk,0 ); +if (bdev) { + error =blkdev_issue_flush (bdev,GFP_KERNEL ,NULL );
block/blk-flush.c void blk_free_flush_queue(struct blk_flush_queue *fq) · line 571
Quoted 10 lines
block/blk-flush.c +10
-0+bdput (bdev); + } + +while (!list_empty (flush_list)) { + rq = list_first_entry(flush_list, struct request, queuelist); +list_del_init (&rq->queuelist); +blk_mq_end_request (rq, error); + } +} +
I must admit I'm getting nervous if one mixes direct request manipulations with high-level 'blkdev_XXX' calls. Can't we just requeue everything including the flush itself, and letting the requeue algorithm pick a new hctx?
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke Teamlead Storage & Networking [email protected] +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
Re: [PATCH V8 08/11] block: add blk_end_flush_machinery
Quoted 136 lines · Hannes Reinecke
Quoted 135 lines · Ming Lei
Flush requests aren't same with normal FS request:
1) one dedicated per-hctx flush rq is pre-allocated for sending flush request
2) flush request si issued to hardware via one machinary so that flush merge can be applied
We can't simply re-submit flush rqs via
blk_steal_bios(), so addblk_end_flush_machineryto collect flush requests which needs to be resubmitted:- if one flush command without DATA is enough, send one flush, complete this kind of requests
- otherwise, add the request into a list and let caller re-submit it.
Cc John Garry <[email protected]>Cc Bart Van Assche <[email protected]>Cc Hannes Reinecke <[email protected]>Cc Christoph Hellwig <[email protected]>Cc Thomas Gleixner <[email protected]>Reviewed-by Christoph Hellwig <[email protected]>Signed-off-by Ming Lei <[email protected]>--- block/blk-flush.c | 123 +++++++++++++++++++++++++++++++++++++++++++--- block/blk.h | 4 ++ 2 files changed, 120 insertions(+), 7 deletions(-)block/blk-flush.c +69
-7@@ -170,10 +170,11 @@ static void blk_flush_complete_seq(struct request *rq,unsigned int cmd_flags;BUG_ON (rq->flush.seq & seq); - rq->flush.seq |= seq; +if (!error) + rq->flush.seq |= seq; cmd_flags = rq->cmd_flags; -if (likely (!error)) +if (likely (!error && !fq->flush_queue_terminating)) seq =blk_flush_cur_seq (rq);else seq =REQ_FSEQ_DONE ;@@ -200,9 +201,15 @@ static void blk_flush_complete_seq(struct request *rq,* normal completion and end it. */ BUG_ON (!list_empty (&rq->queuelist)); -list_del_init (&rq->flush.list); -blk_flush_restore_request (rq); -blk_mq_end_request (rq, error); + +/* Terminating code will end the request from flush queue */ +if (likely (!fq->flush_queue_terminating)) { +list_del_init (&rq->flush.list); +blk_flush_restore_request (rq); +blk_mq_end_request (rq, error); + }else { +list_move_tail (&rq->flush.list, pending); + }break ;default :@@ -279,7 +286,8 @@ static void blk_kick_flush(struct request_queue *q, struct blk_flush_queue *fq,struct request *flush_rq = fq->flush_rq;/* C1 described at the top of this file */ -if (fq->flush_pending_idx != fq->flush_running_idx ||list_empty (pending)) +if (fq->flush_pending_idx != fq->flush_running_idx || +list_empty (pending) || fq->flush_queue_terminating)return ;/* C2 and C3 @@ -331,7 +339,7 @@ static void mq_flush_data_end_io(struct request *rq, blk_status_t error)struct blk_flush_queue *fq =blk_get_flush_queue (q, ctx);if (q->elevator) { -WARN_ON (rq->tag <0 ); +WARN_ON (rq->tag <0 && !fq->flush_queue_terminating);blk_mq_put_driver_tag (rq); }@@ -503,3 +511,104 @@ void blk_free_flush_queue(struct blk_flush_queue *fq)kfree (fq->flush_rq);kfree (fq); } + +static void __blk_end_queued_flush (struct blk_flush_queue *fq, +unsigned int queue_idx,struct list_head *resubmit_list, +struct list_head *flush_list) +{ +struct list_head *queue = &fq->flush_queue[queue_idx]; +struct request *rq, *nxt; + +list_for_each_entry_safe (rq, nxt, queue, flush.list) { +unsigned int seq =blk_flush_cur_seq (rq); + +list_del_init (&rq->flush.list); +blk_flush_restore_request (rq); +if (!blk_rq_sectors (rq) || seq ==REQ_FSEQ_POSTFLUSH ) +list_add_tail (&rq->queuelist, flush_list); +else +list_add_tail (&rq->queuelist, resubmit_list); + } +} + +static void blk_end_queued_flush (struct blk_flush_queue *fq, +struct list_head *resubmit_list,struct list_head *flush_list) +{ +unsigned long flags; + +spin_lock_irqsave (&fq->mq_flush_lock, flags); +__blk_end_queued_flush (fq,0 , resubmit_list, flush_list); +__blk_end_queued_flush (fq,1 , resubmit_list, flush_list); +spin_unlock_irqrestore (&fq->mq_flush_lock, flags); +} + +/* complete requests which just requires one flush command */ +static void blk_complete_flush_requests (struct blk_flush_queue *fq, +struct list_head *flush_list) +{ +struct block_device *bdev; +struct request *rq; +int error = -ENXIO ; + +if (list_empty (flush_list)) +return ; + + rq = list_first_entry(flush_list, struct request, queuelist); + +/* Send flush via one active hctx so we can move on */ + bdev =bdget_disk (rq->rq_disk,0 ); +if (bdev) { + error =blkdev_issue_flush (bdev,GFP_KERNEL ,NULL ); +bdput (bdev); + } + +while (!list_empty (flush_list)) { + rq = list_first_entry(flush_list, struct request, queuelist); +list_del_init (&rq->queuelist);
Quoted 8 lines
block/blk-flush.c void blk_free_flush_queue(struct blk_flush_queue *fq) · line 571
Quoted 4 lines
block/blk-flush.c +4
-0+blk_mq_end_request (rq, error); + } +} +I must admit I'm getting nervous if one mixes direct request manipulations with high-level '
blkdev_XXX' calls.
Can't we just requeue everything including the flush itself, and letting the requeue algorithm pick a new hctx?
No, the biggest problem is that rq->mq_hctx is bound to the hctx(becomes inactive now) since request allocation, so we can't requeue them simply.
What we need here is simply one flush command, blkdev_issue_flush() does exactly what we want.
Thanks,
Ming
PATCH v8 9/11 blk-mq: add blk_mq_hctx_handle_dead_cpu for handling cpu dead
In reply to Ming LeiAdd helper of blk_mq_hctx_handle_dead_cpu for handling cpu dead, and prepare for handling inactive hctx.
No functional change.
--- block/blk-mq.c | 31 +++++++++++++++++++------------ 1 file changed, 19 insertions(+), 12 deletions(-)
block/blk-mq.c +19 -12
@@ -2370,22 +2370,13 @@ static int blk_mq_hctx_notify_online(unsigned int cpu, struct hlist_node *node)return 0 ; } -/* -* 'cpu' is going away. splice any existing rq_list entries from this -* software queue to the hw queue dispatch list, and ensure that it -* gets run. -*/ -static int blk_mq_hctx_notify_dead (unsigned int cpu,struct hlist_node *node) +static void blk_mq_hctx_handle_dead_cpu (struct blk_mq_hw_ctx *hctx, +unsigned int cpu) { -struct blk_mq_hw_ctx *hctx =hlist_entry_safe (node, - struct blk_mq_hw_ctx, cpuhp_dead);struct blk_mq_ctx *ctx;LIST_HEAD (tmp);enum hctx_type type; -if (!cpumask_test_cpu (cpu, hctx->cpumask)) -return 0 ; - ctx =__blk_mq_get_ctx (hctx->queue, cpu); type = hctx->type;
@@ -2397,13 +2388,29 @@ static int blk_mq_hctx_notify_dead(unsigned int cpu, struct hlist_node *node)spin_unlock (&ctx->lock);if (list_empty (&tmp)) -return 0 ; +return ;spin_lock (&hctx->lock);list_splice_tail_init (&tmp, &hctx->dispatch);spin_unlock (&hctx->lock);blk_mq_run_hw_queue (hctx, true); +} + +/* +* 'cpu' is going away. splice any existing rq_list entries from this +* software queue to the hw queue dispatch list, and ensure that it +* gets run. +*/ +static int blk_mq_hctx_notify_dead (unsigned int cpu,struct hlist_node *node) +{ +struct blk_mq_hw_ctx *hctx =hlist_entry_safe (node, + struct blk_mq_hw_ctx, cpuhp_dead); + +if (!cpumask_test_cpu (cpu, hctx->cpumask)) +return 0 ; + +blk_mq_hctx_handle_dead_cpu (hctx, cpu);return 0 ; }
Signature · 1 line
2.25.2
Re: [PATCH V8 09/11] blk-mq: add blk_mq_hctx_handle_dead_cpu for handling cpu dead
block/blk-mq.c static int blk_mq_hctx_notify_dead(unsigned int cpu, struct hlist_node *node) · line 2414
Quoted 10 lines
block/blk-mq.c +9
-0+static int blk_mq_hctx_notify_dead (unsigned int cpu,struct hlist_node *node) +{ +struct blk_mq_hw_ctx *hctx =hlist_entry_safe (node, + struct blk_mq_hw_ctx, cpuhp_dead); + +if (!cpumask_test_cpu (cpu, hctx->cpumask)) +return 0 ; + +blk_mq_hctx_handle_dead_cpu (hctx, cpu);return 0 ;
As commented last time:
why not simply:
if (cpumask_test_cpu(cpu, hctx->cpumask)) blk_mq_hctx_handle_dead_cpu(hctx, cpu); return 0;
?
Re: [PATCH V8 09/11] blk-mq: add blk_mq_hctx_handle_dead_cpu for handling cpu dead
Quoted 13 lines · Christoph Hellwig
block/blk-mq.c static int blk_mq_hctx_notify_dead(unsigned int cpu, struct hlist_node *node) · line 2414
Quoted 10 lines
block/blk-mq.c +9
-0+static int blk_mq_hctx_notify_dead (unsigned int cpu,struct hlist_node *node) +{ +struct blk_mq_hw_ctx *hctx =hlist_entry_safe (node, + struct blk_mq_hw_ctx, cpuhp_dead); + +if (!cpumask_test_cpu (cpu, hctx->cpumask)) +return 0 ; + +blk_mq_hctx_handle_dead_cpu (hctx, cpu);return 0 ;As commented last time:
Quoted 5 lines
why not simply:
if (cpumask_test_cpu(cpu, hctx->cpumask)) blk_mq_hctx_handle_dead_cpu(hctx, cpu); return 0;
Hammm, it is just done on another handler, looks this one is missed.
Thanks,
Ming
Re: [PATCH V8 09/11] blk-mq: add blk_mq_hctx_handle_dead_cpu for handling cpu dead
In reply to Ming LeiQuoted 66 lines · Ming Lei
Add helper of
blk_mq_hctx_handle_dead_cpufor handling cpu dead, and prepare for handling inactive hctx.No functional change.
Cc John Garry <[email protected]>Cc Bart Van Assche <[email protected]>Cc Hannes Reinecke <[email protected]>Cc Christoph Hellwig <[email protected]>Cc Thomas Gleixner <[email protected]>Signed-off-by Ming Lei <[email protected]>--- block/blk-mq.c | 31 +++++++++++++++++++------------ 1 file changed, 19 insertions(+), 12 deletions(-)block/blk-mq.c +12
-12@@ -2370,22 +2370,13 @@ static int blk_mq_hctx_notify_online(unsigned int cpu, struct hlist_node *node)return 0 ; } -/* -* 'cpu' is going away. splice any existing rq_list entries from this -* software queue to the hw queue dispatch list, and ensure that it -* gets run. -*/ -static int blk_mq_hctx_notify_dead (unsigned int cpu,struct hlist_node *node) +static void blk_mq_hctx_handle_dead_cpu (struct blk_mq_hw_ctx *hctx, +unsigned int cpu) { -struct blk_mq_hw_ctx *hctx =hlist_entry_safe (node, - struct blk_mq_hw_ctx, cpuhp_dead);struct blk_mq_ctx *ctx;LIST_HEAD (tmp);enum hctx_type type; -if (!cpumask_test_cpu (cpu, hctx->cpumask)) -return 0 ; - ctx =__blk_mq_get_ctx (hctx->queue, cpu); type = hctx->type;@@ -2397,13 +2388,29 @@ static int blk_mq_hctx_notify_dead(unsigned int cpu, struct hlist_node *node)spin_unlock (&ctx->lock);if (list_empty (&tmp)) -return 0 ; +return ;spin_lock (&hctx->lock);list_splice_tail_init (&tmp, &hctx->dispatch);spin_unlock (&hctx->lock);blk_mq_run_hw_queue (hctx, true); +} + +/* +* 'cpu' is going away. splice any existing rq_list entries from this +* software queue to the hw queue dispatch list, and ensure that it +* gets run. +*/ +static int blk_mq_hctx_notify_dead (unsigned int cpu,struct hlist_node *node) +{
block/blk-mq.c static int blk_mq_hctx_notify_dead(unsigned int cpu, struct hlist_node *node) · line 2416
Quoted 10 lines
block/blk-mq.c +7
-0+struct blk_mq_hw_ctx *hctx =hlist_entry_safe (node, + struct blk_mq_hw_ctx, cpuhp_dead); + +if (!cpumask_test_cpu (cpu, hctx->cpumask)) +return 0 ; + +blk_mq_hctx_handle_dead_cpu (hctx, cpu);return 0 ; }
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke Teamlead Storage & Networking [email protected] +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
PATCH v8 10/11 blk-mq: re-submit IO in case that hctx is inactive
In reply to Ming LeiWhen all CPUs in one hctx are offline and this hctx becomes inactive, we shouldn't run this hw queue for completing request any more.
So allocate request from one live hctx, and clone & resubmit the request, either it is from sw queue or scheduler queue.
--- block/blk-mq.c | 102 +++++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 98 insertions(+), 4 deletions(-)
block/blk-mq.c +98 -4
@@ -2370,6 +2370,98 @@ static int blk_mq_hctx_notify_online(unsigned int cpu, struct hlist_node *node)return 0 ; } +static void blk_mq_resubmit_end_rq (struct request *rq,blk_status_t error) +{ +struct request *orig_rq = rq->end_io_data; + +blk_mq_cleanup_rq (orig_rq); +blk_mq_end_request (orig_rq, error); + +blk_put_request (rq); +} + +static void blk_mq_resubmit_rq (struct request *rq) +{ +struct request *nrq; +unsigned int flags =0 ; +struct blk_mq_hw_ctx *hctx = rq->mq_hctx; +struct blk_mq_tags *tags = rq->q->elevator ? hctx->sched_tags : + hctx->tags; +bool reserved =blk_mq_tag_is_reserved (tags, rq->internal_tag); + +if (rq->rq_flags &RQF_PREEMPT ) + flags |=BLK_MQ_REQ_PREEMPT ; +if (reserved) + flags |=BLK_MQ_REQ_RESERVED ; + +/* avoid allocation failure by clearing NOWAIT */ + nrq =blk_get_request (rq->q, rq->cmd_flags & ~REQ_NOWAIT , flags); +if (!nrq) +return ; + +blk_rq_copy_request (nrq, rq); + + nrq->timeout = rq->timeout; + nrq->rq_disk = rq->rq_disk; + nrq->part = rq->part; + +memcpy (blk_mq_rq_to_pdu (nrq),blk_mq_rq_to_pdu (rq), + rq->q->tag_set->cmd_size); + + nrq->end_io = blk_mq_resubmit_end_rq; + nrq->end_io_data = rq; + nrq->bio = rq->bio; + nrq->biotail = rq->biotail; + +if (blk_insert_cloned_request (nrq->q, nrq) !=BLK_STS_OK ) +blk_mq_request_bypass_insert (nrq, false, true); +} + +static void blk_mq_hctx_deactivate (struct blk_mq_hw_ctx *hctx) +{ +LIST_HEAD (sched); +LIST_HEAD (re_submit); +LIST_HEAD (flush_in); +LIST_HEAD (flush_out); +struct request *rq, *nxt; +struct elevator_queue *e = hctx->queue->elevator; + +if (!e) { +blk_mq_flush_busy_ctxs (hctx, &re_submit); + }else { +while ((rq = e->type->ops.dispatch_request (hctx))) { +if (rq->mq_hctx != hctx) +list_add (&rq->queuelist, &sched); +else +list_add (&rq->queuelist, &re_submit); + } + } +while (!list_empty (&sched)) { + rq = list_first_entry(&sched, struct request, queuelist); +list_del_init (&rq->queuelist); +blk_mq_sched_insert_request (rq, true, true, true); + } + +/* requests in dispatch list have to be re-submitted too */ +spin_lock (&hctx->lock); +list_splice_tail_init (&hctx->dispatch, &re_submit); +spin_unlock (&hctx->lock); + +/* blk_end_flush_machinery will cover flush request */ +list_for_each_entry_safe (rq, nxt, &re_submit, queuelist) { +if (rq->rq_flags &RQF_FLUSH_SEQ ) +list_move (&rq->queuelist, &flush_in); + } +blk_end_flush_machinery (hctx, &flush_in, &flush_out); +list_splice_tail (&flush_out, &re_submit); + +while (!list_empty (&re_submit)) { + rq = list_first_entry(&re_submit, struct request, queuelist); +list_del_init (&rq->queuelist); +blk_mq_resubmit_rq (rq); + } +} +static void blk_mq_hctx_handle_dead_cpu (struct blk_mq_hw_ctx *hctx,unsigned int cpu) {
@@ -2398,9 +2490,8 @@ static void blk_mq_hctx_handle_dead_cpu(struct blk_mq_hw_ctx *hctx, }/* -* 'cpu' is going away. splice any existing rq_list entries from this -* software queue to the hw queue dispatch list, and ensure that it -* gets run. +* @cpu has gone away. If this hctx is inactive, we can't dispatch request +* to the hctx any more, so clone and re-submit requests from this hctx */ static int blk_mq_hctx_notify_dead (unsigned int cpu,struct hlist_node *node) {
@@ -2410,7 +2501,10 @@ static int blk_mq_hctx_notify_dead(unsigned int cpu, struct hlist_node *node)if (!cpumask_test_cpu (cpu, hctx->cpumask))return 0 ; -blk_mq_hctx_handle_dead_cpu (hctx, cpu); +if (test_bit (BLK_MQ_S_INACTIVE , &hctx->state)) +blk_mq_hctx_deactivate (hctx); +else +blk_mq_hctx_handle_dead_cpu (hctx, cpu);return 0 ; }
Signature · 1 line
2.25.2
Re: [PATCH V8 10/11] blk-mq: re-submit IO in case that hctx is inactive
block/blk-mq.c static int blk_mq_hctx_notify_online(unsigned int cpu, struct hlist_node *node) · line 2404
Quoted 8 lines
block/blk-mq.c +8
-0+/* avoid allocation failure by clearing NOWAIT */ + nrq =blk_get_request (rq->q, rq->cmd_flags & ~REQ_NOWAIT , flags); +if (!nrq) +return ; + +blk_rq_copy_request (nrq, rq); + + nrq->timeout = rq->timeout;
Shouldn't the timeout also go into blk_rq_copy_request?
Otherwise this looks good:
Re: [PATCH V8 10/11] blk-mq: re-submit IO in case that hctx is inactive
Quoted 10 lines · Christoph Hellwig
block/blk-mq.c static int blk_mq_hctx_notify_online(unsigned int cpu, struct hlist_node *node) · line 2404
Quoted 8 lines
block/blk-mq.c +8
-0+/* avoid allocation failure by clearing NOWAIT */ + nrq =blk_get_request (rq->q, rq->cmd_flags & ~REQ_NOWAIT , flags); +if (!nrq) +return ; + +blk_rq_copy_request (nrq, rq); + + nrq->timeout = rq->timeout;Shouldn't the timeout also go into
blk_rq_copy_request?
I'd suggest to not do it because dm-rq clones request between two different queues, and different queue may have different default timeout value. And I guess that is why dm-rq code doesn't do that.
Thanks,
Ming
Re: [PATCH V8 10/11] blk-mq: re-submit IO in case that hctx is inactive
In reply to Ming LeiQuoted 43 lines · Ming Lei
When all CPUs in one hctx are offline and this hctx becomes inactive, we shouldn't run this hw queue for completing request any more.
So allocate request from one live hctx, and clone & resubmit the request, either it is from sw queue or scheduler queue.
Cc John Garry <[email protected]>Cc Bart Van Assche <[email protected]>Cc Hannes Reinecke <[email protected]>Cc Christoph Hellwig <[email protected]>Cc Thomas Gleixner <[email protected]>Signed-off-by Ming Lei <[email protected]>--- block/blk-mq.c | 102 +++++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 98 insertions(+), 4 deletions(-)block/blk-mq.c +19
-0@@ -2370,6 +2370,98 @@ static int blk_mq_hctx_notify_online(unsigned int cpu, struct hlist_node *node)return 0 ; } +static void blk_mq_resubmit_end_rq (struct request *rq,blk_status_t error) +{ +struct request *orig_rq = rq->end_io_data; + +blk_mq_cleanup_rq (orig_rq); +blk_mq_end_request (orig_rq, error); + +blk_put_request (rq); +} + +static void blk_mq_resubmit_rq (struct request *rq) +{ +struct request *nrq; +unsigned int flags =0 ; +struct blk_mq_hw_ctx *hctx = rq->mq_hctx; +struct blk_mq_tags *tags = rq->q->elevator ? hctx->sched_tags : + hctx->tags; +bool reserved =blk_mq_tag_is_reserved (tags, rq->internal_tag); +
block/blk-mq.c static int blk_mq_hctx_notify_online(unsigned int cpu, struct hlist_node *node) · line 2401
Quoted 10 lines
block/blk-mq.c +10
-0+if (rq->rq_flags &RQF_PREEMPT ) + flags |=BLK_MQ_REQ_PREEMPT ; +if (reserved) + flags |=BLK_MQ_REQ_RESERVED ; + +/* avoid allocation failure by clearing NOWAIT */ + nrq =blk_get_request (rq->q, rq->cmd_flags & ~REQ_NOWAIT , flags); +if (!nrq) +return ; +
Ah-ha. So what happens if we don't get a request here?
Quoted 8 lines
block/blk-mq.c +8
-0+blk_rq_copy_request (nrq, rq); + + nrq->timeout = rq->timeout; + nrq->rq_disk = rq->rq_disk; + nrq->part = rq->part; + +memcpy (blk_mq_rq_to_pdu (nrq),blk_mq_rq_to_pdu (rq), + rq->q->tag_set->cmd_size);
block/blk-mq.c static int blk_mq_hctx_notify_online(unsigned int cpu, struct hlist_node *node) · line 2419
Quoted 10 lines
block/blk-mq.c +10
-0+ + nrq->end_io = blk_mq_resubmit_end_rq; + nrq->end_io_data = rq; + nrq->bio = rq->bio; + nrq->biotail = rq->biotail; + +if (blk_insert_cloned_request (nrq->q, nrq) !=BLK_STS_OK ) +blk_mq_request_bypass_insert (nrq, false, true); +} +
Not sure if that is a good idea.
With the above code we would having to allocate an additional
tag per request; if we're running full throttle with all tags active where should they be coming from?
And all the while we _have_ perfectly valid tags; the tag of the original request _is_ perfectly valid, and we have made sure that it's not inflight (because if it were we would have to wait for to be completed by the hardware anyway).
So why can't we re-use the existing tag here?
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke Teamlead Storage & Networking [email protected] +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
Re: [PATCH V8 10/11] blk-mq: re-submit IO in case that hctx is inactive
Quoted 47 lines · Hannes Reinecke
Quoted 46 lines · Ming Lei
When all CPUs in one hctx are offline and this hctx becomes inactive, we shouldn't run this hw queue for completing request any more.
So allocate request from one live hctx, and clone & resubmit the request, either it is from sw queue or scheduler queue.
Cc John Garry <[email protected]>Cc Bart Van Assche <[email protected]>Cc Hannes Reinecke <[email protected]>Cc Christoph Hellwig <[email protected]>Cc Thomas Gleixner <[email protected]>Signed-off-by Ming Lei <[email protected]>--- block/blk-mq.c | 102 +++++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 98 insertions(+), 4 deletions(-)block/blk-mq.c +23
-0@@ -2370,6 +2370,98 @@ static int blk_mq_hctx_notify_online(unsigned int cpu, struct hlist_node *node)return 0 ; } +static void blk_mq_resubmit_end_rq (struct request *rq,blk_status_t error) +{ +struct request *orig_rq = rq->end_io_data; + +blk_mq_cleanup_rq (orig_rq); +blk_mq_end_request (orig_rq, error); + +blk_put_request (rq); +} + +static void blk_mq_resubmit_rq (struct request *rq) +{ +struct request *nrq; +unsigned int flags =0 ; +struct blk_mq_hw_ctx *hctx = rq->mq_hctx; +struct blk_mq_tags *tags = rq->q->elevator ? hctx->sched_tags : + hctx->tags; +bool reserved =blk_mq_tag_is_reserved (tags, rq->internal_tag); + +if (rq->rq_flags &RQF_PREEMPT ) + flags |=BLK_MQ_REQ_PREEMPT ; +if (reserved) + flags |=BLK_MQ_REQ_RESERVED ;
Quoted 8 lines
block/blk-mq.c static int blk_mq_hctx_notify_online(unsigned int cpu, struct hlist_node *node) · line 2401
Quoted 6 lines
block/blk-mq.c +6
-0+ +/* avoid allocation failure by clearing NOWAIT */ + nrq =blk_get_request (rq->q, rq->cmd_flags & ~REQ_NOWAIT , flags); +if (!nrq) +return ; +Ah-ha. So what happens if we don't get a request here?
So far it isn't possible if NOWAIT is cleared because the two requests belong to different hctx.
Quoted 16 lines
Quoted 16 lines
block/blk-mq.c +15
-0+blk_rq_copy_request (nrq, rq); + + nrq->timeout = rq->timeout; + nrq->rq_disk = rq->rq_disk; + nrq->part = rq->part; + +memcpy (blk_mq_rq_to_pdu (nrq),blk_mq_rq_to_pdu (rq), + rq->q->tag_set->cmd_size); + + nrq->end_io = blk_mq_resubmit_end_rq; + nrq->end_io_data = rq; + nrq->bio = rq->bio; + nrq->biotail = rq->biotail; + +if (blk_insert_cloned_request (nrq->q, nrq) !=BLK_STS_OK )
Quoted 8 lines
block/blk-mq.c static int blk_mq_hctx_notify_online(unsigned int cpu, struct hlist_node *node) · line 2419
Quoted 3 lines
block/blk-mq.c +3
-0+blk_mq_request_bypass_insert (nrq, false, true); +} +Not sure if that is a good idea.
With the above code we would having to allocate an additional tag per request; if we're running full throttle with all tags active where should they be coming from?
The two requests are from different hctx, and we don't have per-request-queue throttle in blk-mq, and scsi does have, however no requests from this inactive hctx exists in LLD.
So no the throttle you worry about.
Quoted 3 lines
And all the while we _have_ perfectly valid tags; the tag of the original request _is_ perfectly valid, and we have made sure that it's not inflight
No, we are talking request in sw queue and scheduler queue, which aren't assigned tag yet.
Quoted 4 lines
(because if it were we would have to wait for to be completed by the hardware anyway).
So why can't we re-use the existing tag here?
No, the tag doesn't exist.
Thanks,
Ming
PATCH v8 11/11 block: deactivate hctx when the hctx is actually inactive
In reply to Ming LeiRun queue on dead CPU still may be triggered in some corner case, such as one request is requeued after CPU hotplug is handled.
So handle this corner case during run queue.
--- block/blk-mq.c | 30 ++++++++++-------------------- 1 file changed, 10 insertions(+), 20 deletions(-)
block/blk-mq.c +10 -20
@@ -43,6 +43,8 @@static void blk_mq_poll_stats_start (struct request_queue *q);static void blk_mq_poll_stats_fn (struct blk_stat_callback *cb); +static void blk_mq_hctx_deactivate (struct blk_mq_hw_ctx *hctx); +static int blk_mq_poll_stats_bkt (const struct request *rq) {int ddir, sectors, bucket;
@@ -1376,28 +1378,16 @@ static void __blk_mq_run_hw_queue(struct blk_mq_hw_ctx *hctx)int srcu_idx;/* -* We should be running this queue from one of the CPUs that -* are mapped to it. -* -* There are at least two related races now between setting -* hctx->next_cpu from blk_mq_hctx_next_cpu() and running -* __blk_mq_run_hw_queue(): -* -* - hctx->next_cpu is found offline in blk_mq_hctx_next_cpu(), -* but later it becomes online, then this warning is harmless -* at all -* -* - hctx->next_cpu is found online in blk_mq_hctx_next_cpu(), -* but later it becomes offline, then the warning can't be -* triggered, and we depend on blk-mq timeout handler to -* handle dispatched requests to this hctx +* BLK_MQ_S_INACTIVE may not deal with some requeue corner case: +* one request is requeued after cpu unplug is handled, so check +* if the hctx is actually inactive. If yes, deactive it and +* re-submit all requests in the queue. */ if (!cpumask_test_cpu (raw_smp_processor_id (), hctx->cpumask) && -cpu_online (hctx->next_cpu)) { -printk (KERN_WARNING "run queue from wrong CPU %d, hctx %s\n" , -raw_smp_processor_id (), -cpumask_empty (hctx->cpumask) ?"inactive" :"active" ); -dump_stack (); +cpumask_next_and (-1 , hctx->cpumask, cpu_online_mask) >= + nr_cpu_ids) { +blk_mq_hctx_deactivate (hctx); +return ; }/*
Signature · 1 line
2.25.2
Re: [PATCH V8 11/11] block: deactivate hctx when the hctx is actually inactive
Quoted 4 lines · Ming Lei
Run queue on dead CPU still may be triggered in some corner case, such as one request is requeued after CPU hotplug is handled.
So handle this corner case during run queue.
Looks good,
Re: [PATCH V8 11/11] block: deactivate hctx when the hctx is actually inactive
In reply to Ming LeiQuoted 56 lines · Ming Lei
Run queue on dead CPU still may be triggered in some corner case, such as one request is requeued after CPU hotplug is handled.
So handle this corner case during run queue.
Cc John Garry <[email protected]>Cc Bart Van Assche <[email protected]>Cc Hannes Reinecke <[email protected]>Cc Christoph Hellwig <[email protected]>Cc Thomas Gleixner <[email protected]>Signed-off-by Ming Lei <[email protected]>--- block/blk-mq.c | 30 ++++++++++-------------------- 1 file changed, 10 insertions(+), 20 deletions(-)block/blk-mq.c +6
-17@@ -43,6 +43,8 @@static void blk_mq_poll_stats_start (struct request_queue *q);static void blk_mq_poll_stats_fn (struct blk_stat_callback *cb); +static void blk_mq_hctx_deactivate (struct blk_mq_hw_ctx *hctx); +static int blk_mq_poll_stats_bkt (const struct request *rq) {int ddir, sectors, bucket;@@ -1376,28 +1378,16 @@ static void __blk_mq_run_hw_queue(struct blk_mq_hw_ctx *hctx)int srcu_idx;/* -* We should be running this queue from one of the CPUs that -* are mapped to it. -* -* There are at least two related races now between setting -* hctx->next_cpu from blk_mq_hctx_next_cpu() and running -* __blk_mq_run_hw_queue(): -* -* - hctx->next_cpu is found offline in blk_mq_hctx_next_cpu(), -* but later it becomes online, then this warning is harmless -* at all -* -* - hctx->next_cpu is found online in blk_mq_hctx_next_cpu(), -* but later it becomes offline, then the warning can't be -* triggered, and we depend on blk-mq timeout handler to -* handle dispatched requests to this hctx +* BLK_MQ_S_INACTIVE may not deal with some requeue corner case: +* one request is requeued after cpu unplug is handled, so check +* if the hctx is actually inactive. If yes, deactive it and +* re-submit all requests in the queue. */ if (!cpumask_test_cpu(raw_smp_processor_id(), hctx->cpumask) && -cpu_online (hctx->next_cpu)) { - printk(KERN_WARNING "run queue from wrong CPU %d, hctx %s\n",
block/blk-mq.c static void __blk_mq_run_hw_queue(struct blk_mq_hw_ctx *hctx) · line 1393
Quoted 10 lines
block/blk-mq.c +4
-3-raw_smp_processor_id (), - cpumask_empty(hctx->cpumask) ? "inactive": "active"); -dump_stack (); + cpumask_next_and(-1, hctx->cpumask, cpu_online_mask) >= + nr_cpu_ids) { +blk_mq_hctx_deactivate (hctx); +return ; }/*
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke Teamlead Storage & Networking [email protected] +49 911 74053 688 SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer
Jens Axboe
maintainerQuoted 27 lines · Ming Lei
Hi,
Thomas mentioned:
"
That was the constraint of managed interrupts from the very beginning:The driver/subsystem has to quiesce the interrupt line and the associated queue _before_ it gets shutdown in CPU unplug and not fiddle with it until it's restarted by the core when the CPU is plugged in again.
"But no drivers or blk-mq do that before one hctx becomes inactive(all CPUs for one hctx are offline), and even it is worse, blk-mq stills tries to run hw queue after hctx is dead, see
blk_mq_hctx_notify_dead().This patchset tries to address the issue by two stages:
1) add one new cpuhp state of
CPUHP_AP_BLK_MQ_ONLINE- mark the hctx as internal stopped, and drain all in-flight requests if the hctx is going to be dead.
2) re-submit IO in the state of
CPUHP_BLK_MQ_DEADafter the hctx becomes dead- steal bios from the request, and resubmit them via
generic_make_request(), then these IO will be mapped to other live hctx for dispatch
Quoted 6 lines
Thanks John Garry for running lots of tests on arm64 with this patchset and co-working on investigating all kinds of issues.
Thanks Christoph's review on V7.
Please comment & review, thanks!
Applied for 5.8 - had to do it manually for the first two patches, as they conflict with the dma drain removal from core from Christoph.
Signature · 1 line
Jens Axboe
Quoted 4 lines · Jens Axboe
Quoted 1 line
Please comment & review, thanks!
Applied for 5.8 - had to do it manually for the first two patches, as they conflict with the dma drain removal from core from Christoph.
I'd really like to see the barrier mess sorted out before this is merged..
Jens Axboe
maintainerQuoted 8 lines · Christoph Hellwig
Quoted 4 lines · Jens Axboe
Quoted 1 line
Please comment & review, thanks!
Applied for 5.8 - had to do it manually for the first two patches, as they conflict with the dma drain removal from core from Christoph.
I'd really like to see the barrier mess sorted out before this is merged..
OK, we can hold off until that's sorted.
Signature · 1 line
Jens Axboe