From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Srujana Challa <schalla@marvell.com>, dev@dpdk.org, chenbox@nvidia.com
Cc: jerinj@marvell.com, ndabilpuram@marvell.com, vattunuru@marvell.com
Subject: Re: [PATCH v2 0/3] net/virtio: support IOVA as PA mode for vDPA backend
Date: Fri, 28 Jun 2024 15:33:37 +0200 [thread overview]
Message-ID: <02b57186-7c6b-4f31-ab03-19033bf24c15@redhat.com> (raw)
In-Reply-To: <20240229132919.2186118-1-schalla@marvell.com>
On 2/29/24 14:29, Srujana Challa wrote:
> 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(-)
>
I think we need a way to be able to perform the address translation from
iova to va between Virtio and Virtio-user layers. Does that sound
reasonable?
Thanks,
Maxime
prev parent reply other threads:[~2024-06-28 13:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 13:29 Srujana Challa
2024-02-29 13:29 ` [PATCH v2 1/3] net/virtio_user: avoid cq descriptor buffer address accessing Srujana Challa
2024-06-28 8:07 ` Maxime Coquelin
2024-07-02 11:09 ` [EXTERNAL] " Srujana Challa
2024-07-02 12:41 ` Maxime Coquelin
2024-07-03 10:03 ` [PATCH v3 0/3] net/virtio: support IOVA as PA mode for vDPA backend Srujana Challa
2024-07-03 10:03 ` [PATCH v3 1/3] net/virtio_user: convert cq descriptor IOVA address to Virtual address Srujana Challa
2024-07-03 10:19 ` Jerin Jacob
2024-07-03 13:28 ` Maxime Coquelin
2024-07-12 11:22 ` David Marchand
2024-07-03 13:40 ` Maxime Coquelin
2024-07-10 15:06 ` David Marchand
2024-07-11 8:54 ` [EXTERNAL] " Srujana Challa
2024-07-03 10:03 ` [PATCH v3 2/3] net/virtio: store desc IOVA address in vring data structure Srujana Challa
2024-07-03 13:41 ` Maxime Coquelin
2024-07-03 10:03 ` [PATCH v3 3/3] net/virtio_user: support sharing vq descriptor IOVA to the backend Srujana Challa
2024-07-03 13:41 ` Maxime Coquelin
2024-07-03 14:34 ` [PATCH v3 0/3] net/virtio: support IOVA as PA mode for vDPA backend Maxime Coquelin
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
2024-06-19 9:39 ` [PATCH v2 0/3] net/virtio: support IOVA as PA mode for vDPA backend Srujana Challa
2024-06-28 13:33 ` Maxime Coquelin [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=02b57186-7c6b-4f31-ab03-19033bf24c15@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=schalla@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).