From: Christoph Hellwig <hch@lst.de>
To: David Epping <david.epping@missinglinkelectronics.com>
Cc: Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org, Jens Axboe <axboe@kernel.dk>,
Sagi Grimberg <sagi@grimberg.me>,
Leon Romanovsky <leon@kernel.org>,
Joachim Foerster <joachim.foerster@missinglinkelectronics.com>
Subject: Re: [PATCH RFC] nvme-ioctl: propagate PRP1 from ioctl to admin cmd
Date: Mon, 29 Jun 2026 14:28:23 +0200 [thread overview]
Message-ID: <20260629122823.GE21344@lst.de> (raw)
In-Reply-To: <akJiSTxXC84z4KiT@ubuntu-server>
On Mon, Jun 29, 2026 at 02:20:27PM +0200, David Epping wrote:
> Keith, thank you for the follow up and catching my mistake. I noticed the
> missing R and just assumed its a typo... Sorry.
> I will absolutely look into SIOV to understand the concept!
Note that SIOV would indeed be very interesting for these use cases,
but it requires spec work and hardware support. The NVMe technical
working group is looking into a proposal for it at the moment.
next prev parent reply other threads:[~2026-06-29 12:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 14:15 [PATCH RFC] nvme-ioctl: propagate PRP1 from ioctl to admin cmd David Epping
2026-06-22 14:35 ` Keith Busch
2026-06-22 14:56 ` David Epping
2026-06-22 15:15 ` Keith Busch
2026-06-23 10:34 ` David Epping
2026-06-23 12:19 ` Keith Busch
2026-06-24 7:40 ` Christoph Hellwig
2026-06-26 17:55 ` David Epping
2026-06-26 22:22 ` Keith Busch
2026-06-29 12:20 ` David Epping
2026-06-29 12:28 ` Christoph Hellwig [this message]
2026-06-29 9:05 ` 顾泽兵
2026-06-29 13:02 ` David Epping
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=20260629122823.GE21344@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=david.epping@missinglinkelectronics.com \
--cc=joachim.foerster@missinglinkelectronics.com \
--cc=kbusch@kernel.org \
--cc=leon@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--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.