From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, stable@dpdk.org, chenbo.xia@intel.com,
amorenoz@redhat.com, jasowang@redhat.com,
david.marchand@redhat.com
Subject: Re: [dpdk-dev] [PATCH v3 0/2] Vhost-vDPA fixes
Date: Mon, 11 Jan 2021 15:59:41 +0100 [thread overview]
Message-ID: <1d857a15-5fe9-05d2-6889-b58e0266372d@redhat.com> (raw)
In-Reply-To: <20210108094149.215384-1-maxime.coquelin@redhat.com>
On 1/8/21 10:41 AM, Maxime Coquelin wrote:
> Vhost-vDPA support in Virtio-user PMD was lacking
> backend features negotiation and IOTLB batching
> support, causing intialization issues with Mellanox
> vDPA device managed by Kernel vDPA framework.
>
> Changes in v3:
> =============
> - Fix protocol features negotiation condition (Chenbo)
> - Fixup comment in struct declaration (Chenbo)
>
> Changes in v2:
> =============
> - Add backend features negotiation (David, Jason)
> - Ensure Kernel supports IOTLB MSG v2
>
> Maxime Coquelin (2):
> net/virtio: fix missing backend features negotiation
> net/virtio: fix memory init with vDPA backend
>
> drivers/net/virtio/virtio_user/vhost.h | 8 ++
> drivers/net/virtio/virtio_user/vhost_vdpa.c | 120 +++++++++++++++++-
> .../net/virtio/virtio_user/virtio_user_dev.c | 15 ++-
> .../net/virtio/virtio_user/virtio_user_dev.h | 4 +-
> 4 files changed, 135 insertions(+), 12 deletions(-)
>
Applied to dpdk-next-virtio/main.
Thanks,
Maxime
prev parent reply other threads:[~2021-01-11 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 9:41 Maxime Coquelin
2021-01-08 9:41 ` [dpdk-dev] [PATCH v3 1/2] net/virtio: fix missing backend features negotiation Maxime Coquelin
2021-01-11 5:43 ` Xia, Chenbo
2021-01-08 9:41 ` [dpdk-dev] [PATCH v3 2/2] net/virtio: fix memory init with vDPA backend Maxime Coquelin
2021-01-11 14:59 ` 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=1d857a15-5fe9-05d2-6889-b58e0266372d@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=amorenoz@redhat.com \
--cc=chenbo.xia@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jasowang@redhat.com \
--cc=stable@dpdk.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 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).