public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v7 0/4] vhost-user,tcp: Handle multiple iovec entries per virtqueue element
Date: Tue, 26 May 2026 14:44:50 +0200 (CEST)	[thread overview]
Message-ID: <20260526144450.492c6554@elisabeth> (raw)
In-Reply-To: <20260520151010.496286-1-lvivier@redhat.com>

On Wed, 20 May 2026 17:10:06 +0200
Laurent Vivier <lvivier@redhat.com> wrote:

> This is the TCP counterpart to the UDP multi-iov series.  It converts
> the TCP vhost-user receive path from direct pointer arithmetic (via
> vu_eth(), vu_ip(), etc.) to the iov_tail abstraction, removing the
> assumption that all headers reside in a single contiguous buffer.
> 
> With this series applied, the TCP path correctly handles virtio-net
> drivers that provide multiple buffers per virtqueue element (e.g. iPXE
> provides the vnet header in the first buffer and the frame payload in a
> second one), matching the support already present in the UDP path.
> 
> Based-on: 20260520095526.21519-1-lvivier@redhat.com
> 
> v7:
> - Use initializers for struct tcphdr
> - Rename reused 'payload' variable to 'l2frame'
> - Fix vu_pad() double-offset bug in tcp_vu_data_from_sock()
> - Remove redundant *elem_used = 0 before truncation loop
> - Add missing @vnlen to tcp_vu_send_dup() doc comment

Applied.

-- 
Stefano


      parent reply	other threads:[~2026-05-26 12:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-20 15:10 Laurent Vivier
2026-05-20 15:10 ` [PATCH v7 1/4] tcp: Encode checksum computation flags in a single parameter Laurent Vivier
2026-05-26  8:37   ` Stefano Brivio
2026-05-26  8:56     ` Laurent Vivier
2026-05-26 12:44 ` Stefano Brivio [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=20260526144450.492c6554@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=passt-dev@passt.top \
    /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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

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 IMAP folder(s).