From: "Maurizio Lombardi" <mlombard@arkamax.eu>
To: "Daniel Wagner" <dwagner@suse.de>,
"Maurizio Lombardi" <mlombard@redhat.com>
Cc: <kbusch@kernel.org>, <mheyne@amazon.de>, <emilne@redhat.com>,
<jmeneghi@redhat.com>, <linux-nvme@lists.infradead.org>,
<mlombard@arkamax.eu>, <mkhalfella@purestorage.com>,
<chaitanyak@nvidia.com>, <hare@kernel.org>, <hch@lst.de>
Subject: Re: [PATCH V3 4/8] nvme: add sysfs attribute to change IO timeout per nvme controller
Date: Mon, 27 Apr 2026 11:13:43 +0200 [thread overview]
Message-ID: <DI3TM2S46GYN.38E7GIF26O7GD@arkamax.eu> (raw)
In-Reply-To: <d776e448-461d-4888-a685-a9af79c61d9c@flourine.local>
On Mon Apr 27, 2026 at 11:11 AM CEST, Daniel Wagner wrote:
> On Fri, Apr 10, 2026 at 09:39:20AM +0200, Maurizio Lombardi wrote:
>> Currently, there is no method to adjust the timeout values on a
>> per controller basis with nvme I/O queues.
>> Add an io_timeout attribute to nvme so that different nvme controllers
>> which may have different timeout requirements can have custom
>> I/O timeouts set.
>>
>> Signed-off-by: Maurizio Lombardi <mlombard@redhat.com>
>> ---
>> drivers/nvme/host/core.c | 2 ++
>> drivers/nvme/host/nvme.h | 1 +
>> drivers/nvme/host/sysfs.c | 47 +++++++++++++++++++++++++++++++++++++++
>> 3 files changed, 50 insertions(+)
>>
>> diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
>> index 6dc3d273623c..1b676fd4d454 100644
>> --- a/drivers/nvme/host/core.c
>> +++ b/drivers/nvme/host/core.c
>> @@ -4197,6 +4197,7 @@ static void nvme_alloc_ns(struct nvme_ctrl *ctrl, struct nvme_ns_info *info)
>> mutex_unlock(&ctrl->namespaces_lock);
>> goto out_unlink_ns;
>> }
>> + blk_queue_rq_timeout(ns->queue, ctrl->io_timeout);
>> nvme_ns_add_to_ctrl_list(ns);
>> mutex_unlock(&ctrl->namespaces_lock);
>> synchronize_srcu(&ctrl->srcu);
>> @@ -5136,6 +5137,7 @@ int nvme_init_ctrl(struct nvme_ctrl *ctrl, struct device *dev,
>> ctrl->ka_cmd.common.opcode = nvme_admin_keep_alive;
>> ctrl->ka_last_check_time = jiffies;
>> ctrl->admin_timeout = NVME_ADMIN_TIMEOUT;
>> + ctrl->io_timeout = NVME_IO_TIMEOUT;
>
> Should this be initialized with the defaults from the module load time?
Yes, note that NVME_IO_TIMEOUT is a macro that depends on the
"nvme_io_timeout" module parameter set at load time.
Maurizio
next prev parent reply other threads:[~2026-04-27 9:13 UTC|newest]
Thread overview: 38+ 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-22 9:58 ` Daniel Wagner
2026-04-24 13:38 ` Christoph Hellwig
2026-04-10 7:39 ` [PATCH V3 2/8] nvme: add sysfs attribute to change admin timeout per nvme controller Maurizio Lombardi
2026-04-22 10:10 ` Daniel Wagner
2026-04-22 11:08 ` Maurizio Lombardi
2026-04-23 12:46 ` Daniel Wagner
2026-04-23 12:58 ` Maurizio Lombardi
2026-04-23 17:04 ` Daniel Wagner
2026-04-23 18:35 ` Maurizio Lombardi
2026-04-23 13:45 ` Hannes Reinecke
2026-04-10 7:39 ` [PATCH V3 3/8] nvme: pci: use admin queue timeout over NVME_ADMIN_TIMEOUT Maurizio Lombardi
2026-04-27 9:05 ` Daniel Wagner
2026-04-10 7:39 ` [PATCH V3 4/8] nvme: add sysfs attribute to change IO timeout per nvme controller Maurizio Lombardi
2026-04-24 13:40 ` Christoph Hellwig
2026-04-27 9:11 ` Daniel Wagner
2026-04-27 9:13 ` Maurizio Lombardi [this message]
2026-04-27 9:19 ` Daniel Wagner
2026-04-28 17:23 ` Mohamed Khalfella
2026-04-29 12:06 ` 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-27 9:22 ` Daniel Wagner
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-27 9:35 ` Daniel Wagner
2026-04-10 7:39 ` [PATCH V3 7/8] nvmet-loop: do not alloc admin tag set during reset Maurizio Lombardi
2026-04-27 9:46 ` Daniel Wagner
2026-04-27 9:47 ` Maurizio Lombardi
2026-04-28 11:17 ` Maurizio Lombardi
2026-04-28 12:46 ` Daniel Wagner
2026-05-07 16:23 ` Daniel Wagner
2026-05-08 6:14 ` 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-24 13:40 ` Christoph Hellwig
2026-04-27 9:54 ` Daniel Wagner
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
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=DI3TM2S46GYN.38E7GIF26O7GD@arkamax.eu \
--to=mlombard@arkamax.eu \
--cc=chaitanyak@nvidia.com \
--cc=dwagner@suse.de \
--cc=emilne@redhat.com \
--cc=hare@kernel.org \
--cc=hch@lst.de \
--cc=jmeneghi@redhat.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mheyne@amazon.de \
--cc=mkhalfella@purestorage.com \
--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