DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Chenbo Xia <chenbox@nvidia.com>,
	Jay Zhou <jianjay.zhou@huawei.com>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>,
	Anoob Joseph <anoobj@marvell.com>,
	Akhil Goyal <gakhil@marvell.com>,
	Jerin Jacob <jerinj@marvell.com>,
	Fan Zhang <fanzhang.oss@gmail.com>,
	Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: RE: [RFC] crypto/virtio: add vhost-vdpa backend
Date: Wed, 27 Nov 2024 06:50:23 +0000	[thread overview]
Message-ID: <CO1PR18MB4714A72F8CE3F1E517B1C352CB282@CO1PR18MB4714.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20241121180219.1234-1-gmuthukrishn@marvell.com>

Hi,
I wanted to follow up on my previous message regarding the development of a vhost vDPA host driver for crypto/virtio. We have proposed creating a driver/common/virtio/ directory to hold common implementations for both net and crypto functionalities. This approach aims to help in fixing common issues and extending virtio functionalities efficiently.

As we plan to include this feature in DPDK 25.03, we would like to conclude on the implementation direction soon. We would greatly appreciate your valuable feedback or any suggestions on this proposal. Thank you!

Thanks,
Gowrishankar

> Hi,
> We are adding support for vDPA user backend for virtio-crypto PMD in DPDK.
> We have come up with functional changes which is similar to the support
> available in net:
> 
>     commit 6b901437056eed3ed7c9932c333ba24ac5be116f
> 
>     net/virtio: introduce vhost-vDPA backend
>     vhost-vDPA is a new virtio backend type introduced by vDPA kernel
>     framework, which provides abstraction to the vDPA devices and
>     exposes an unified control interface through a char dev.
> 
> Our current development reuses some code from net/virtio/virtio_user/, and
> we realize that we could keep a few things in common between net and
> crypto, such as:
> 
> -> vhost_vdpa.c (and its header file) from net/virtio/virtio_user/:
>    Except for VHOST_VDPA_GET_DEVICE_ID and enabling queue pairs,
> virtio_user_backend_ops can be reused.
> -> virtio_user_dev.c (and its header file) from net/virtio/virtio_user/:
>    virtio_user_dev_init and its capabilities differ.
> -> virtio_cvq.c (and its header file) from net/virtio/:
>    There is a difference in the usage of the first and last descriptors for the virtio
> header and status (net vs. crypto).
> 
> We need to standardize these codes to ensure they work universally.
> Therefore, we propose creating a driver/common/virtio/ directory to house
> them. This approach will help address common issues and extend Virtio
> functionalities shared between crypto and net. For example, the crypto PMD
> can benefit from packed ring support. We welcome your valuable feedback
> and any suggestions.
> 
> Thanks,
> Gowrishankar
> --
> 2.37.1


  reply	other threads:[~2024-11-27  6:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21 18:02 Gowrishankar Muthukrishnan
2024-11-27  6:50 ` Gowrishankar Muthukrishnan [this message]
2024-11-27  7:52   ` Chenbo Xia
2024-11-27  8:10 ` Jason Wang

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=CO1PR18MB4714A72F8CE3F1E517B1C352CB282@CO1PR18MB4714.namprd18.prod.outlook.com \
    --to=gmuthukrishn@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=chenbox@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=fanzhang.oss@gmail.com \
    --cc=gakhil@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=jianjay.zhou@huawei.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=ndabilpuram@marvell.com \
    --cc=techboard@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).