From: Stefano Brivio <sbrivio@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v11 0/3] vhost-user,udp: Handle multiple iovec entries per virtqueue element
Date: Tue, 26 May 2026 14:44:33 +0200 (CEST) [thread overview]
Message-ID: <20260526144431.0dfd9ec2@elisabeth> (raw)
In-Reply-To: <20260520095526.21519-1-lvivier@redhat.com>
On Wed, 20 May 2026 11:55:23 +0200
Laurent Vivier <lvivier@redhat.com> wrote:
> Some virtio-net drivers (notably iPXE) provide descriptors where the
> vnet header and the frame payload are in separate buffers, resulting in
> two iovec entries per virtqueue element. Currently, the RX (host to
> guest) path assumes a single iovec per element, which triggers:
>
> ASSERTION FAILED in virtqueue_map_desc (virtio.c:403):
> num_sg < max_num_sg
>
> This series reworks the UDP vhost-user receive path to support multiple
> iovec entries per element, fixing the iPXE crash.
>
> This series only addresses the UDP path. TCP vhost-user will be
> updated to use multi-iov elements in a subsequent series.
>
> v11:
> - Rebase on master
> - use sizeof(*uh) instead of sizeof(struct udphdr) in
> udp_tap_prepare()
> - improve @payload doc in udp_vu_sock_recv()
> - add R-b from David
Applied.
--
Stefano
prev 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 9:55 Laurent Vivier
2026-05-20 9:55 ` [PATCH v11 1/3] udp_vu: Allow virtqueue elements with multiple iovec entries Laurent Vivier
2026-05-20 9:55 ` [PATCH v11 2/3] iov: Introduce IOV_PUSH_HEADER() macro Laurent Vivier
2026-05-20 9:55 ` [PATCH v11 3/3] udp: Pass iov_tail to udp_update_hdr4()/udp_update_hdr6() 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=20260526144431.0dfd9ec2@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).