From: Christoph Hellwig <hch@lst.de>
To: chengming.zhou@linux.dev
Cc: axboe@kernel.dk, ming.lei@redhat.com, hch@lst.de, tj@kernel.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Chengming Zhou <zhouchengming@bytedance.com>
Subject: Re: [PATCH v2 1/4] blk-mq: use percpu csd to remote complete instead of per-rq csd
Date: Thu, 6 Jul 2023 15:07:35 +0200 [thread overview]
Message-ID: <20230706130735.GA13089@lst.de> (raw)
In-Reply-To: <20230629110359.1111832-2-chengming.zhou@linux.dev>
On Thu, Jun 29, 2023 at 07:03:56PM +0800, chengming.zhou@linux.dev wrote:
> From: Chengming Zhou <zhouchengming@bytedance.com>
>
> If request need to be completed remotely, we insert it into percpu llist,
> and smp_call_function_single_async() if llist is empty previously.
>
> We don't need to use per-rq csd, percpu csd is enough. And the size of
> struct request is decreased by 24 bytes.
>
> This way is cleaner, and looks correct, given block softirq is guaranteed to be
> scheduled to consume the list if one new request is added to this percpu list,
> either smp_call_function_single_async() returns -EBUSY or 0.
Please trim your commit logs to 73 characters per line so that they
are readable in git log output.
> static void blk_mq_request_bypass_insert(struct request *rq,
> @@ -1156,13 +1157,13 @@ static void blk_mq_complete_send_ipi(struct request *rq)
> {
> struct llist_head *list;
> unsigned int cpu;
> + call_single_data_t *csd;
>
> cpu = rq->mq_ctx->cpu;
> list = &per_cpu(blk_cpu_done, cpu);
> - if (llist_add(&rq->ipi_list, list)) {
> - INIT_CSD(&rq->csd, __blk_mq_complete_request_remote, rq);
> - smp_call_function_single_async(cpu, &rq->csd);
> - }
> + csd = &per_cpu(blk_cpu_csd, cpu);
> + if (llist_add(&rq->ipi_list, list))
> + smp_call_function_single_async(cpu, csd);
> }
No need for the list and csd variables here as they are only used
once.
But I think this code has a rpboem when it is preemptd between
the llist_add and smp_call_function_single_async. We either need a
get_cpu/put_cpu around them, or instroduce a structure with the list
and csd, and then you can use one pointer from per_cpu and still ensure
the list and csd are for the same CPU.
next prev parent reply other threads:[~2023-07-06 13:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 11:03 [PATCH v2 0/4] blk-mq: optimize the size of struct request chengming.zhou
2023-06-29 11:03 ` [PATCH v2 1/4] blk-mq: use percpu csd to remote complete instead of per-rq csd chengming.zhou
2023-07-05 15:01 ` Ming Lei
2023-07-06 13:07 ` Christoph Hellwig [this message]
2023-07-06 14:23 ` Chengming Zhou
2023-07-06 14:39 ` Christoph Hellwig
2023-06-29 11:03 ` [PATCH v2 2/4] blk-flush: count inflight flush_data requests chengming.zhou
2023-07-05 15:10 ` Ming Lei
2023-07-06 13:08 ` Christoph Hellwig
2023-06-29 11:03 ` [PATCH v2 3/4] blk-flush: reuse rq queuelist in flush state machine chengming.zhou
2023-07-06 13:08 ` Christoph Hellwig
2023-06-29 11:03 ` [PATCH v2 4/4] blk-mq: delete unused completion_data in struct request chengming.zhou
2023-07-06 13:08 ` Christoph Hellwig
2023-07-06 14:31 ` Chengming Zhou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230706130735.GA13089@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=chengming.zhou@linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=tj@kernel.org \
--cc=zhouchengming@bytedance.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox