[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2ed2dadc-bdc4-4a21-8aca-a2aac0c6479a@acm.org>
Date: Thu, 21 Mar 2024 12:52:19 -0700
From: Bart Van Assche <bvanassche@....org>
To: Christian Loehle <christian.loehle@....com>,
Qais Yousef <qyousef@...alina.io>
Cc: linux-kernel@...r.kernel.org, peterz@...radead.org,
juri.lelli@...hat.com, mingo@...hat.com, rafael@...nel.org,
dietmar.eggemann@....com, vschneid@...hat.com, vincent.guittot@...aro.org,
Johannes.Thumshirn@....com, adrian.hunter@...el.com, ulf.hansson@...aro.org,
andres@...razel.de, asml.silence@...il.com, linux-pm@...r.kernel.org,
linux-block@...r.kernel.org, io-uring@...r.kernel.org,
linux-mmc@...r.kernel.org
Subject: Re: [RFC PATCH 0/2] Introduce per-task io utilization boost
On 3/21/24 10:57, Christian Loehle wrote:
> In the long-term it looks like for UFS the problem will disappear as we are
> expected to get one queue/hardirq per CPU (as Bart mentioned), on NVMe that
> is already the case.
Why the focus on storage controllers with a single completion interrupt?
It probably won't take long (one year?) until all new high-end
smartphones may have support for multiple completion interrupts.
Thanks,
Bart.
Powered by blists - more mailing lists