DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, david.marchand@redhat.com, chenbox@nvidia.com
Subject: Re: [PATCH v3 0/3] vhost: fix and improve dequeue error path
Date: Fri, 17 Jan 2025 10:31:17 +0100	[thread overview]
Message-ID: <2bfdf232-c159-455a-8392-043ac32479a8@redhat.com> (raw)
In-Reply-To: <20250116095416.3655699-1-maxime.coquelin@redhat.com>



On 1/16/25 10:54 AM, Maxime Coquelin wrote:
> This series starts with a fix for a regression in the Vhost
> dequeue error path.
> 
> The other patches improve the error handling to reduce the
> chance of such regressions in the future.
> 
> Changes in v3:
> ==============
> - Squashed patches 2 & 3 (David)
> - Simplify RARP handling further (David
> 
> Changes in v2:
> ==============
> - Add RARP handling refactoring
> 
> Maxime Coquelin (3):
>    vhost: fix missing packets count reset when not ready
>    vhost: rework dequeue paths error handling
>    vhost: improve RARP handling in dequeue paths
> 
>   lib/vhost/virtio_net.c | 110 ++++++++++++++++++-----------------------
>   1 file changed, 47 insertions(+), 63 deletions(-)
> 
Applied to next-virtio/for-next-net

Thanks,
Maxime


      parent reply	other threads:[~2025-01-17  9:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16  9:54 Maxime Coquelin
2025-01-16  9:54 ` [PATCH v3 1/3] vhost: fix missing packets count reset when not ready Maxime Coquelin
2025-01-16 10:10   ` David Marchand
2025-01-16 12:14   ` Chenbo Xia
2025-01-16  9:54 ` [PATCH v3 2/3] vhost: rework dequeue paths error handling Maxime Coquelin
2025-01-16 10:10   ` David Marchand
2025-01-16 12:15   ` Chenbo Xia
2025-01-16  9:54 ` [PATCH v3 3/3] vhost: improve RARP handling in dequeue paths Maxime Coquelin
2025-01-16 10:12   ` David Marchand
2025-01-16 12:15   ` Chenbo Xia
2025-01-16 13:08   ` David Marchand
2025-01-17  9:31 ` 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=2bfdf232-c159-455a-8392-043ac32479a8@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).