Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Guixin Liu <kanie@linux.alibaba.com>
To: Martin George <martinus.gpy@gmail.com>,
	Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
	Nilay Shroff <nilay@linux.ibm.com>,
	Daniel Wagner <dwagner@suse.de>, Hannes Reinecke <hare@suse.de>
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH v3 3/3] nvme: document the service-time iopolicy sysfs attributes
Date: Mon, 26 Oct 2026 10:09:07 +0800	[thread overview]
Message-ID: <50def86f-d791-4207-8058-5129ee4ccc93@linux.alibaba.com> (raw)
In-Reply-To: <ec1327b1fcad832c065db8aad1b987ff6437cc2f.camel@gmail.com>



在 2026/10/24 18:37, Martin George 写道:
> On Fri, 2026-10-23 at 15:02 +0800, Guixin Liu wrote:
>>  		Shows or sets the multipath I/O path selection
>> policy for
>>  		this subsystem. Accepted values: "numa", "round-
>> robin",
>> -		"queue-depth". Changing the policy clears all
>> current path
>> -		selections. Only available when
>> CONFIG_NVME_MULTIPATH is
>> -		enabled.
>> +		"queue-depth", "service-time". Changing the policy
>> clears
>> +		all current path selections. Only available when
>> +		CONFIG_NVME_MULTIPATH is enabled.
>>  
>>  What:		/sys/class/nvme-subsystem/nvme-subsysX/subsystype
>>  Date:		September 2021
> Same nit as before. Looks like only the iopolicy documentation is
> updated above with the new 'service-time' policy, but not the
> iopolicies documentation. Have you drafted these patches against the
> latest nvme-7.4 branch itself?
>
> -Martin
Sorry, my bad, I didn't understand your true meaning before, I will
rebase my branch to nvme-7.4, and add an another patch for iopolicies.

Best Regards,
Guixin Liu



      reply	other threads:[~2026-10-26  2:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23  7:02 [PATCH v3 0/3] nvme: introduce the service-time iopolicy Guixin Liu
2026-10-23  7:02 ` [PATCH v3 1/3] nvme-multipath: implement " Guixin Liu
2026-10-23  7:02 ` [PATCH v3 2/3] nvme-multipath: document " Guixin Liu
2026-10-23  7:02 ` [PATCH v3 3/3] nvme: document the service-time iopolicy sysfs attributes Guixin Liu
2026-10-24 10:37   ` Martin George
2026-10-26  2:09     ` Guixin Liu [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=50def86f-d791-4207-8058-5129ee4ccc93@linux.alibaba.com \
    --to=kanie@linux.alibaba.com \
    --cc=axboe@kernel.dk \
    --cc=dwagner@suse.de \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=martinus.gpy@gmail.com \
    --cc=nilay@linux.ibm.com \
    --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