DPDK patches and discussions
 help / color / mirror / Atom feed
From: Srujana Challa <schalla@marvell.com>
To: <dev@dpdk.org>, <maxime.coquelin@redhat.com>, <chenbox@nvidia.com>
Cc: <jerinj@marvell.com>, <ndabilpuram@marvell.com>,
	<vattunuru@marvell.com>,  <schalla@marvell.com>
Subject: [PATCH v2 0/3] net/virtio: support IOVA as PA mode for vDPA backend
Date: Thu, 29 Feb 2024 18:59:16 +0530	[thread overview]
Message-ID: <20240229132919.2186118-1-schalla@marvell.com> (raw)

This patch series makes Virtio-user works in IOVA as PA mode
for vDPA backend.

First patch fixes the issue when having buffer IOVA address in
control queue descriptors.
Second and third patches helps to share descriptor IOVA address,
to the vhost backend. And also disables the use_va flag for VDPA
backend type.

v1->v2:
- Split single patch into three patches.

Srujana Challa (3):
  net/virtio_user: avoid cq descriptor buffer address accessing
  net/virtio: store desc IOVA address in vring data structure
  net/virtio_user: support sharing vq descriptor IOVA to the backend

 drivers/net/virtio/virtio_ring.h              | 12 ++-
 .../net/virtio/virtio_user/virtio_user_dev.c  | 94 ++++++++++---------
 drivers/net/virtio/virtio_user_ethdev.c       | 10 +-
 drivers/net/virtio/virtqueue.c                |  4 +-
 4 files changed, 69 insertions(+), 51 deletions(-)

-- 
2.25.1


             reply	other threads:[~2024-02-29 13:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 13:29 Srujana Challa [this message]
2024-02-29 13:29 ` [PATCH v2 1/3] net/virtio_user: avoid cq descriptor buffer address accessing Srujana Challa
2024-02-29 13:29 ` [PATCH v2 2/3] net/virtio: store desc IOVA address in vring data structure Srujana Challa
2024-02-29 13:29 ` [PATCH v2 3/3] net/virtio_user: support sharing vq descriptor IOVA to the backend Srujana Challa

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=20240229132919.2186118-1-schalla@marvell.com \
    --to=schalla@marvell.com \
    --cc=chenbox@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=ndabilpuram@marvell.com \
    --cc=vattunuru@marvell.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).