From: Stefan Hajnoczi <stefanha@redhat.com>
To: 侯英乐 <houyingle@sudoinfotech.com>
Cc: jasowang <jasowang@redhat.com>,
David Hildenbrand <david@redhat.com>,
virtio-comment <virtio-comment@lists.oasis-open.org>,
Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
Kevin Wolf <kwolf@redhat.com>,
Klaus Jensen <k.jensen@samsung.com>,
sgarzare <sgarzare@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: Re: [virtio-comment] About adding a new device type virtio-nvme
Date: Thu, 19 Jan 2023 12:03:02 -0500 [thread overview]
Message-ID: <Y8l3xu7ZdXVgD84C@fedora> (raw)
In-Reply-To: <9E1AD7FE8906C9F0+2023011917033819334533@sudoinfotech.com>
[-- Attachment #1: Type: text/plain, Size: 2177 bytes --]
On Thu, Jan 19, 2023 at 05:03:38PM +0800, 侯英乐 wrote:
> Wed, 18 Jan 2023 09:14:41 -0500, Stefan wrote:
>
> >On Wed, Jan 18, 2023 at 10:15:12AM +0800, 侯英乐 wrote:
>
> >> On Tue, 17 Jan 2023 10:34:09 -0500, Stefan wrote:
>
> >> >On Tue, Jan 17, 2023 at 05:41:57PM +0800, 侯英乐 wrote:
>
> >> >> On Tue, 17 Jan 2023 09:32:05 +0100,David wrote:
>
> >> >> >On 17.01.23 03:04, 侯英乐 wrote:
>
> >> >The two diagrams are quite similar. Did you want to highlight a
>
> >>
>
> >> >difference between the two approaches in the diagram?
>
> >>
>
> >> The biggest difference is the VFIO and vDPA frameworks. The vDPA (virtio data path acceleration) kernel framework
>
> >> is a pillar in productizing the end-to-end vDPA solution and it enables NIC vendors to integrate their vDPA NIC kernel
>
> >> drivers into the framework as part of their productization efforts.
>
> >> Detailed information reference:https://www.redhat.com/en/blog/introduction-vdpa-kernel-framework
>
>
>
> >For the sake of the argument, let's assume VFIO can't be used in your
>
> >situation so vDPA is required. The part I don't understand is which
>
> >specific NVMe features you need that virtio-blk lacks?
>
>
>
> During the DPU chip design process, "Fabrics connect" commands are not supported on standard nvme-pci devices,
> but I can be delivered to remote storage at the back-end of the nvme-pci device.
>
> In the case of a virtio-blk device, I am not clear how the back-end of virtio-blk connects to remote storage.Although
> NVIDIA claims to support virtio-blk SNAP (Software-defined Network Accelerated Processing), their implementation
> is not expected to be an open source standard, other vendors may have developed based on proprietary specifications.
>
> All of this is from a hardware offloading perspective. There are two solutions to the problem I'm facing:
Wait, what is the problem you are facing? Why do you need NVMe?
> 1) virtio combines nvme, add a new virtio-nvme device.
> 2) virtio-blk Adds Fabrics related commands to enable virtio-blk to support Virtio-blk-of (over Fabric).
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-01-19 17:03 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 3:21 [virtio-comment] About adding a new device type virtio-nvme 侯英乐
2023-01-11 15:16 ` Stefan Hajnoczi
2023-01-17 2:04 ` 侯英乐
2023-01-17 8:32 ` David Hildenbrand
2023-01-17 9:30 ` 侯英乐
[not found] ` <202301171730174296359@sudoinfotech.com>
2023-01-17 9:41 ` 侯英乐
2023-01-17 15:34 ` Stefan Hajnoczi
2023-01-17 15:47 ` David Hildenbrand
2023-01-18 2:38 ` 侯英乐
2023-01-18 2:15 ` 侯英乐
2023-01-18 14:08 ` Stefan Hajnoczi
2023-01-19 8:31 ` 侯英乐
2023-01-18 14:14 ` Stefan Hajnoczi
2023-01-19 3:40 ` Jason Wang
2023-01-19 16:59 ` Stefan Hajnoczi
2023-01-19 9:03 ` 侯英乐
2023-01-19 17:03 ` Stefan Hajnoczi [this message]
2023-01-19 3:38 ` Jason Wang
2023-01-19 7:22 ` 侯英乐
2023-01-17 16:01 ` Stefan Hajnoczi
[not found] ` <20230117162114.GA24976@lst.de>
2023-01-17 16:53 ` Stefan Hajnoczi
2023-01-18 11:22 ` Michael S. Tsirkin
2023-01-18 2:49 ` 侯英乐
2023-02-05 12:33 ` Michael S. Tsirkin
2023-02-09 3:28 ` 侯英乐
2023-02-17 3:01 ` Parav Pandit
2023-01-19 11:42 ` Michael S. Tsirkin
2023-01-29 3:32 ` 侯英乐
2023-01-30 20:30 ` Stefan Hajnoczi
2023-01-17 17:19 ` Max Gurtovoy
2023-01-18 3:23 ` 侯英乐
2023-01-18 10:09 ` Max Gurtovoy
2023-01-18 11:12 ` Michael S. Tsirkin
2023-01-18 11:27 ` Max Gurtovoy
2023-01-18 13:29 ` Michael S. Tsirkin
2023-01-19 10:19 ` 侯英乐
2023-01-19 10:33 ` Max Gurtovoy
2023-01-19 11:02 ` 侯英乐
2023-01-19 17:15 ` Stefan Hajnoczi
2023-01-18 10:28 ` Michael S. Tsirkin
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=Y8l3xu7ZdXVgD84C@fedora \
--to=stefanha@redhat.com \
--cc=david@redhat.com \
--cc=hch@lst.de \
--cc=houyingle@sudoinfotech.com \
--cc=jasowang@redhat.com \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=sgarzare@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
/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.