From: Bart Van Assche <bvanassche@acm.org>
To: Christian Loehle <christian.loehle@arm.com>,
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 09:47:17 -0400 [thread overview]
Message-ID: <03e92755-2011-4c43-8a1c-f1ad9a1382eb@acm.org> (raw)
In-Reply-To: <7661afec-168d-406e-903b-a2dc9adf6408@arm.com>
On 8/28/24 8:26 AM, Christian Loehle wrote:
> On 8/28/24 13:13, Bart Van Assche wrote:
>> 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.
Hmm ... is there any x86 architecture that ignores the smp_affinity
mask? I have not yet encountered an x86 system that does not respect
the smp_affinity mask.
Thanks,
Bart.
next prev parent reply other threads:[~2024-08-28 13:47 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
2024-08-28 13:47 ` Bart Van Assche [this message]
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=03e92755-2011-4c43-8a1c-f1ad9a1382eb@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=christian.loehle@arm.com \
--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