From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, david.marchand@redhat.com, chenbox@nvidia.com
Subject: Re: [PATCH v2 0/4] Virtio-user queues setup fixes
Date: Wed, 12 Jun 2024 10:40:29 +0200 [thread overview]
Message-ID: <fa45af8d-6b7e-48bf-9a8a-2d580518e927@redhat.com> (raw)
In-Reply-To: <20240328130813.3696005-1-maxime.coquelin@redhat.com>
On 3/28/24 14:08, Maxime Coquelin wrote:
> This series aims at fixing several issues found in
> Virtio-user PMD related to queues setup and cleanup.
>
> It has been tested with Vhost-vDPA backend using Nvidia
> Cx6-Dx vDPA VF.
>
> First patch in the series renames the queues iterator
> helper, so it is not a fix. But I would suggest to have it
> backported to ease backporting of the fixes.
>
> Changes in v2:
> --------------
> - Fix regression in patch 4 reported by CI
> - Prefix titles with net/virtio-user (David)
> - Reword patch 2 title (David)
> - Apply David acks on patches 1-3
>
> Maxime Coquelin (4):
> net/virtio-user: rename queue iterator
> net/virtio-user: fix control queue destruction
> net/virtio-user: fix shadow control queue notification init
> net/virtio-user: fix control queue allocation
>
> .../net/virtio/virtio_user/virtio_user_dev.c | 133 +++++++++---------
> 1 file changed, 68 insertions(+), 65 deletions(-)
>
Applied to next-virtio/for-next-net.
Thanks,
Maxime
prev parent reply other threads:[~2024-06-12 8:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 13:08 [PATCH v2 0/4] Virtio-user queues setup fixes Maxime Coquelin
2024-03-28 13:08 ` [PATCH v2 1/4] net/virtio-user: rename queue iterator Maxime Coquelin
2024-03-28 13:08 ` [PATCH v2 2/4] net/virtio-user: fix control queue destruction Maxime Coquelin
2024-03-28 13:08 ` [PATCH v2 3/4] net/virtio-user: fix shadow control queue notification init Maxime Coquelin
2024-03-28 13:08 ` [PATCH v2 4/4] net/virtio-user: fix control queue allocation Maxime Coquelin
2024-06-11 9:02 ` David Marchand
2024-06-12 8:40 ` 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=fa45af8d-6b7e-48bf-9a8a-2d580518e927@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=chenbox@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@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).