From: Christoph Hellwig <hch@lst.de>
To: Mike Christie <michael.christie@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
hare@kernel.org, Keith Busch <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [RFC PATCH 0/6] nvme multipath eBPF path selector
Date: Wed, 30 Jul 2025 16:06:39 +0200 [thread overview]
Message-ID: <20250730140639.GA11278@lst.de> (raw)
In-Reply-To: <ad394458-29ac-4302-8028-2276519a4122@oracle.com>
On Tue, Jul 29, 2025 at 09:53:09AM -0500, Mike Christie wrote:
> On 7/29/25 2:54 AM, Christoph Hellwig wrote:
> > On Tue, Jul 29, 2025 at 09:06:47AM +0200, hare@kernel.org wrote:
> >> From: Hannes Reinecke <hare@kernel.org>
> >>
> >> Hi all,
> >>
> >> there are discussion on having to deploy more complex I/O scheduling
> >> algorithms for NVMe,
> >
> > Are "we"? Where?
>
> I think that's me. I was originally looking into eBPF path selectors
> for ADNN:
>
> https://www.snia.org/educational-library/adaptive-distributed-nvme-namespaces-2020
ADNN needs to use eBPF, but controller provided eBPF, not from the user.
This has been clearly communicated to the group in 2022, but as usual
FMDS is drifting off into their own parallel universe, not only on the
issue of path selection. Based on these factors ADNN in it's current
trajectory is unlikely to ever be implemented in Linux.
next prev parent reply other threads:[~2025-07-30 14:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 7:06 [RFC PATCH 0/6] nvme multipath eBPF path selector hare
2025-07-29 7:06 ` [PATCH 1/6] nvme-multipath: do not assign ->current_path in __nvme_find_path() hare
2025-07-29 7:06 ` [PATCH 2/6] nvme: export nvme_find_get_subsystem()/nvme_put_subsystem() hare
2025-07-29 7:06 ` [PATCH 3/6] nvme: add per-namespace iopolicy sysfs attribute hare
2025-07-29 7:06 ` [PATCH 4/6] nvme: add 'sector' parameter to nvme_find_path() hare
2025-07-29 7:06 ` [PATCH 5/6] nvme-bpf: eBPF struct_ops path selectors hare
2025-07-29 7:06 ` [PATCH 6/6] tools/testing/selftests: add sample nvme bpf path selector hare
2025-07-30 2:03 ` Geliang Tang
2025-07-30 5:56 ` Hannes Reinecke
2025-07-29 7:54 ` [RFC PATCH 0/6] nvme multipath eBPF " Christoph Hellwig
2025-07-29 14:53 ` Mike Christie
2025-07-30 14:06 ` Christoph Hellwig [this message]
2025-07-30 2:03 ` Geliang Tang
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=20250730140639.GA11278@lst.de \
--to=hch@lst.de \
--cc=hare@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=michael.christie@oracle.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;
as well as URLs for NNTP newsgroup(s).