From: Christoph Hellwig <hch@infradead.org>
To: Wadim Mueller <wafgo01@gmail.com>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Jens Axboe" <axboe@kernel.dk>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Damien Le Moal" <dlemoal@kernel.org>,
"Shunsuke Mie" <mie@igel.co.jp>,
linux-pci@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH 0/3] Add support for Block Passthrough Endpoint function driver
Date: Mon, 26 Feb 2024 03:08:19 -0800 [thread overview]
Message-ID: <ZdxxI7bqdajK3Hb7@infradead.org> (raw)
In-Reply-To: <20240224210409.112333-1-wafgo01@gmail.com>
Please don't just create a new (and as far as I can tell underspecified)
new "hardware" interface for this. If the nvme endpoint work is too
much for your use case maybe just implement a minimal virtio_blk
interface.
prev parent reply other threads:[~2024-02-26 11:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 21:03 [PATCH 0/3] Add support for Block Passthrough Endpoint function driver Wadim Mueller
2024-02-24 21:04 ` [PATCH 1/3] PCI: Add PCI Endpoint function driver for Block-device passthrough Wadim Mueller
2024-02-24 21:04 ` [PATCH 2/3] PCI: Add PCI driver for a PCI EP remote Blockdevice Wadim Mueller
2024-02-24 21:04 ` [PATCH 3/3] Documentation: PCI: Add documentation for the PCI Block Passthrough Wadim Mueller
2024-02-25 16:09 ` [PATCH 0/3] Add support for Block Passthrough Endpoint function driver Manivannan Sadhasivam
2024-02-25 20:39 ` Wadim Mueller
2024-02-26 9:45 ` Manivannan Sadhasivam
2024-02-26 12:58 ` Damien Le Moal
2024-02-26 18:47 ` Wadim Mueller
2024-09-25 9:23 ` Manivannan Sadhasivam
2024-02-26 16:47 ` Frank Li
2024-02-26 11:08 ` 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=ZdxxI7bqdajK3Hb7@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=dlemoal@kernel.org \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mie@igel.co.jp \
--cc=wafgo01@gmail.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;
as well as URLs for NNTP newsgroup(s).