From: John Meneghini <jmeneghi@redhat.com>
To: Maurizio Lombardi <mlombard@arkamax.eu>,
Hannes Reinecke <hare@suse.de>,
Maurizio Lombardi <mlombard@redhat.com>,
kbusch@kernel.org
Cc: mheyne@amazon.de, emilne@redhat.com,
linux-nvme@lists.infradead.org, dwagner@suse.de,
mkhalfella@purestorage.com, chaitanyak@nvidia.com,
hare@kernel.org, hch@lst.de
Subject: Re: [PATCH V3 0/8] nvme: Refactor and expose per-controller timeout configuration
Date: Tue, 14 Apr 2026 15:14:48 -0400 [thread overview]
Message-ID: <cd6f6857-729f-40ff-b3be-51db3225d983@redhat.com> (raw)
In-Reply-To: <DHRX0LGNILAX.LTFZVPDRLGOH@arkamax.eu>
On 4/13/26 5:21 AM, Maurizio Lombardi wrote:
> it's worth noting that unless I am missing something the user can already
> trigger this exact scenario today by setting an I/O timeout lower than KATO,
> using the global nvme_io_timeout module parameter.
This is true.
prev parent reply other threads:[~2026-04-14 19:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 7:39 [PATCH V3 0/8] nvme: Refactor and expose per-controller timeout configuration Maurizio Lombardi
2026-04-10 7:39 ` [PATCH V3 1/8] nvme: Let the blocklayer set timeouts for requests Maurizio Lombardi
2026-04-10 7:39 ` [PATCH V3 2/8] nvme: add sysfs attribute to change admin timeout per nvme controller Maurizio Lombardi
2026-04-10 7:39 ` [PATCH V3 3/8] nvme: pci: use admin queue timeout over NVME_ADMIN_TIMEOUT Maurizio Lombardi
2026-04-10 7:39 ` [PATCH V3 4/8] nvme: add sysfs attribute to change IO timeout per nvme controller Maurizio Lombardi
2026-04-10 7:39 ` [PATCH V3 5/8] nvme: use per controller timeout waits over depending on global default Maurizio Lombardi
2026-04-10 7:39 ` [PATCH V3 6/8] nvme-core: align fabrics_q teardown with admin_q in nvme_free_ctrl Maurizio Lombardi
2026-04-10 7:39 ` [PATCH V3 7/8] nvmet-loop: do not alloc admin tag set during reset Maurizio Lombardi
2026-04-10 7:39 ` [PATCH V3 8/8] nvme-core: warn on allocating admin tag set with existing queue Maurizio Lombardi
2026-04-13 8:12 ` [PATCH V3 0/8] nvme: Refactor and expose per-controller timeout configuration Hannes Reinecke
2026-04-13 9:21 ` Maurizio Lombardi
2026-04-14 19:14 ` John Meneghini [this message]
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=cd6f6857-729f-40ff-b3be-51db3225d983@redhat.com \
--to=jmeneghi@redhat.com \
--cc=chaitanyak@nvidia.com \
--cc=dwagner@suse.de \
--cc=emilne@redhat.com \
--cc=hare@kernel.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mheyne@amazon.de \
--cc=mkhalfella@purestorage.com \
--cc=mlombard@arkamax.eu \
--cc=mlombard@redhat.com \
/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