From: Bart Van Assche <bvanassche@acm.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
Ricky WU <ricky_wu@realtek.com>,
Matthew Schwartz <matthew.schwartz@linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
linux-block <linux-block@vger.kernel.org>
Subject: Re: [BUG] - Short freezes in gameplay due to MMC_CAP_AGGRESSIVE_PM on RTS525A card reader
Date: Tue, 3 Feb 2026 10:10:55 -0800 [thread overview]
Message-ID: <2d3b720c-5637-45e7-887d-077b1e9b3c23@acm.org> (raw)
In-Reply-To: <CAPDyKFrNHc4FexuTbdWM-Kvo0mn9C51nJN5b=e0jZR8miFho+g@mail.gmail.com>
On 2/3/26 3:28 AM, Ulf Hansson wrote:
> I guess the question then is, do we always want zero latency, which I
> assume must be costly from a power savings point of view. At least
> during the idle period, while not serving I/O and waiting for the
> device to be runtime suspended.
Block I/O latency suffers if a CPU core enters a lower power state while
waiting for an I/O completion. Hence the choice in the UFS driver for
not allowing CPU cores to enter a lower power state while any block I/O
is in progress.
Bart.
next prev parent reply other threads:[~2026-02-03 18:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 21:01 Matthew Schwartz
2026-01-03 11:37 ` Ulf Hansson
2026-01-03 19:52 ` Matthew Schwartz
2026-01-04 0:45 ` Matthew Schwartz
2026-01-05 3:58 ` Ricky WU
2026-01-05 4:53 ` Matthew Schwartz
2026-01-05 7:02 ` Ricky WU
2026-01-05 7:50 ` Matthew Schwartz
2026-01-05 8:39 ` Ricky WU
2026-01-28 13:23 ` Ulf Hansson
2026-01-28 17:14 ` Bart Van Assche
2026-01-29 16:30 ` Ulf Hansson
2026-02-02 22:47 ` Bart Van Assche
2026-02-03 11:28 ` Ulf Hansson
2026-02-03 18:10 ` Bart Van Assche [this message]
2026-02-05 11:26 ` Ulf Hansson
2026-02-05 14:21 ` Bart Van Assche
2026-02-05 14:55 ` Ulf Hansson
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=2d3b720c-5637-45e7-887d-077b1e9b3c23@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=matthew.schwartz@linux.dev \
--cc=ricky_wu@realtek.com \
--cc=ulf.hansson@linaro.org \
/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
all inboxes | Powered by JetHome®