From: Christoph Hellwig <hch@lst.de>
To: loberman@redhat.com
Cc: kbusch@kernel.org, hch@lst.de, sagi@grimberg.me,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme-multipath: add iopolicies sysfs attribute
Date: Mon, 21 Sep 2026 08:55:55 +0200 [thread overview]
Message-ID: <20260921065555.GA13785@lst.de> (raw)
In-Reply-To: <20260920164000.45508-1-loberman@redhat.com>
On Sun, Sep 20, 2026 at 12:40:00PM -0400, loberman@redhat.com wrote:
> From: Laurence Oberman <loberman@redhat.com>
>
> The subsystem iopolicy attribute only shows the active policy, so
> there is no way to see which policies are available. The block layer
> solves this for I/O schedulers by listing all options with the
> active one in brackets in queue/scheduler.
>
> Changing the output of iopolicy the same way would break existing
> userspace, since nvme-cli compares the value against a bare policy
> name. Leave iopolicy unchanged and add a read-only iopolicies
> attribute that gives equivalent visibility:
Given that we already have a file for the current iopolicy, can we
kill the [ ] notation that makes it hard to machine parse the value?
prev parent reply other threads:[~2026-09-21 6:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 16:40 [PATCH] nvme-multipath: add iopolicies sysfs attribute loberman
2026-09-21 6:55 ` Christoph Hellwig [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=20260921065555.GA13785@lst.de \
--to=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=loberman@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.