mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ferran Duarri <ferran.duarri@me.com>
To: Alexey Bogoslavsky <Alexey.Bogoslavsky@sandisk.com>,
	Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Cc: Yehuda Hahn <Yehuda.Hahn@sandisk.com>,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
	Ferran Duarri <ferran.duarri@me.com>
Subject: Re: [PATCH] nvme: lower default APST max latency to 25ms
Date: Mon, 31 Aug 2026 15:17:00 +0200	[thread overview]
Message-ID: <20260831131701.200793-1-ferran.duarri@me.com> (raw)
In-Reply-To: <DS4PR16MB692456B5425BE0974054C45692AD2@DS4PR16MB6924.namprd16.prod.outlook.com>

Alexey - thanks, that's a real point I hadn't considered: if EXLAT is
deliberately inflated to keep Windows on ps3, the 100ms default isn't a bug,
it's aligned with what vendors actually tuned for.

The measurement itself I think still holds - it's reading what the drive's
live APST table targets, not just trusting the label, and the wake cost at
ps4 was real regardless of why 43ms is the number on the tin. But that's a
different question from whether Linux should default away from it.

What's the OEM precedent you mentioned - did lowering the bound before break
something specific, or was it more general pushback? Trying to understand if
this needs to stay a boot-time opt-in (which it already is via
default_ps_max_latency_us) rather than ever being a compiled default, on any
hardware.

Also - sorry for the fourth copy of this patch landing in your inbox on the
28th. That was a bookkeeping failure on my end, not a deliberate re-post; it
went out after your reply had already arrived and should not have.

Cheers,
Ferran

  reply	other threads:[~2026-08-31 13:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 19:54 Ferran Duarri
2026-08-27 18:52 ` Alexey Bogoslavsky
2026-08-31 13:17   ` Ferran Duarri [this message]
2026-08-31 15:05     ` Alexey Bogoslavsky
  -- strict thread matches above, loose matches on Subject: below --
2026-08-28  9:48 Ferran Duarri
2026-08-20 20:04 Ferran Duarri
2026-08-20 19:44 Ferran Duarri

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=20260831131701.200793-1-ferran.duarri@me.com \
    --to=ferran.duarri@me.com \
    --cc=Alexey.Bogoslavsky@sandisk.com \
    --cc=Yehuda.Hahn@sandisk.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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®