From: Christian Loehle <christian.loehle@arm.com>
To: Bart Van Assche <bvanassche@acm.org>,
Manish Pandey <quic_mapa@quicinc.com>,
Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
quic_nitirawa@quicinc.com, quic_bhaskarv@quicinc.com,
quic_narepall@quicinc.com, quic_rampraka@quicinc.com,
quic_cang@quicinc.com, quic_nguyenb@quicinc.com,
Qais Yousef <qyousef@layalina.io>,
Dietmar Eggemann <dietmar.eggemann@arm.com>
Subject: Re: [PATCH] blk-mq: Allow complete locally if capacities are different
Date: Wed, 28 Aug 2024 13:26:47 +0100 [thread overview]
Message-ID: <7661afec-168d-406e-903b-a2dc9adf6408@arm.com> (raw)
In-Reply-To: <c5d0966b-7de3-4eff-9310-d9a31d822dad@acm.org>
On 8/28/24 13:13, Bart Van Assche wrote:
> On 8/28/24 7:49 AM, Manish Pandey wrote:
>> 'Commit af550e4c9682 ("block/blk-mq: Don't complete locally if
>> capacities are different")' enforces to complete the request locally
>> only if the submission and completion CPUs have same capacity.
>>
>> To have optimal IO load balancing or to avoid contention b/w submission
>> path and completion path, user may need to complete IO request of large
>> capacity CPU(s) on Small Capacity CPU(s) or vice versa.
>>
>> Hence introduce a QUEUE_FLAG_ALLOW_DIFF_CAPACITY blk queue flag to let
>> user decide if it wants to complete the request locally or need an IPI
>> even if the capacity of the requesting and completion queue is different.
>> This gives flexibility to user to choose best CPU for their completion
>> to give best performance for their system.
Why have the flag be
QUEUE_FLAG_ALLOW_DIFF_CAPACITY
instead of just
QUEUE_FLAG_SAME_LLC
so it isn't as HMP specifically-worded?
(And of course then having QUEUE_FLAG_SAME_COMP be strictly
stronger than QUEUE_FLAG_SAME_LLC. On !HMP they are equal.)
That would also answer Bart's question below how this is
different to rq_affinity=0.
>
> I think that the following is missing from the above description:
> - Mentioning that this is for an unusual interrupt routing technology
> (SoC sends the interrupt to another CPU core than what has been
> specified in the smp_affinity mask).
FWIW on !mcq that doesn't have to be the case.
> - An explanation why the desired effect cannot be achieved by changing
> rq_affinity into 0.
>
>> block/blk-mq-debugfs.c | 1 +
>> block/blk-mq.c | 3 ++-
>> block/blk-sysfs.c | 12 ++++++++++--
>> include/linux/blkdev.h | 1 +
>> 4 files changed, 14 insertions(+), 3 deletions(-)
>
> Since the semantics of a sysfs attribute are modified,
> Documentation/ABI/stable/sysfs-block should be updated.
>
> Thanks,
>
> Bart.
>
next prev parent reply other threads:[~2024-08-28 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 11:49 [PATCH] blk-mq: Allow complete locally if capacities are different Manish Pandey
2024-08-28 12:13 ` Bart Van Assche
2024-08-28 12:26 ` Christian Loehle [this message]
2024-08-28 13:47 ` Bart Van Assche
2024-09-01 17:32 ` Qais Yousef
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=7661afec-168d-406e-903b-a2dc9adf6408@arm.com \
--to=christian.loehle@arm.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dietmar.eggemann@arm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_bhaskarv@quicinc.com \
--cc=quic_cang@quicinc.com \
--cc=quic_mapa@quicinc.com \
--cc=quic_narepall@quicinc.com \
--cc=quic_nguyenb@quicinc.com \
--cc=quic_nitirawa@quicinc.com \
--cc=quic_rampraka@quicinc.com \
--cc=qyousef@layalina.io \
/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