public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Laurent Vivier <lvivier@redhat.com>
To: passt-dev@passt.top
Cc: Laurent Vivier <lvivier@redhat.com>
Subject: [PATCH 00/12] vhost-user,udp: Handle multiple iovec entries per virtqueue element
Date: Fri, 27 Feb 2026 15:03:18 +0100	[thread overview]
Message-ID: <20260227140330.2216753-1-lvivier@redhat.com> (raw)

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.

Laurent Vivier (12):
  iov: Add iov_tail_truncate() and iov_tail_zero_end()
  vhost-user: Use ARRAY_SIZE(elem) instead of VIRTQUEUE_MAX_SIZE
  udp_vu: Use iov_tail to manage virtqueue buffers
  udp_vu: Move virtqueue management from udp_vu_sock_recv() to its
    caller
  iov: Add IOV_PUT_HEADER() to write header data back to iov_tail
  udp: Pass iov_tail to udp_update_hdr4()/udp_update_hdr6()
  udp_vu: Use iov_tail in udp_vu_prepare()
  vu_common: Pass iov_tail to vu_set_vnethdr()
  vu_common: Accept explicit iovec counts in vu_set_element()
  vu_common: Accept explicit iovec count per element in vu_init_elem()
  vu_common: Prepare to use multibuffer with guest RX
  vhost-user,udp: Use 2 iovec entries per element

 iov.c          |  58 +++++++++++++++
 iov.h          |  16 +++-
 tcp_vu.c       |  18 +++--
 udp.c          |  65 ++++++++---------
 udp_internal.h |  10 ++-
 udp_vu.c       | 194 +++++++++++++++++++++++++------------------------
 vu_common.c    |  82 +++++++++++++--------
 vu_common.h    |  20 +++--
 8 files changed, 282 insertions(+), 181 deletions(-)

-- 
2.53.0



             reply	other threads:[~2026-02-27 14:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27 14:03 Laurent Vivier [this message]
2026-02-27 14:03 ` [PATCH 01/12] iov: Add iov_tail_truncate() and iov_tail_zero_end() Laurent Vivier
2026-03-01 23:47   ` David Gibson
2026-02-27 14:03 ` [PATCH 02/12] vhost-user: Use ARRAY_SIZE(elem) instead of VIRTQUEUE_MAX_SIZE Laurent Vivier
2026-03-01 23:48   ` David Gibson
2026-02-27 14:03 ` [PATCH 03/12] udp_vu: Use iov_tail to manage virtqueue buffers Laurent Vivier
2026-03-02  0:03   ` David Gibson
2026-02-27 14:03 ` [PATCH 04/12] udp_vu: Move virtqueue management from udp_vu_sock_recv() to its caller Laurent Vivier
2026-03-02  0:05   ` David Gibson
2026-02-27 14:03 ` [PATCH 05/12] iov: Add IOV_PUT_HEADER() to write header data back to iov_tail Laurent Vivier
2026-03-02  0:08   ` David Gibson
2026-02-27 14:03 ` [PATCH 06/12] udp: Pass iov_tail to udp_update_hdr4()/udp_update_hdr6() Laurent Vivier
2026-03-02  0:13   ` David Gibson
2026-02-27 14:03 ` [PATCH 07/12] udp_vu: Use iov_tail in udp_vu_prepare() Laurent Vivier
2026-03-02  0:24   ` David Gibson
2026-02-27 14:03 ` [PATCH 08/12] vu_common: Pass iov_tail to vu_set_vnethdr() Laurent Vivier
2026-03-02  0:51   ` David Gibson
2026-02-27 14:03 ` [PATCH 09/12] vu_common: Accept explicit iovec counts in vu_set_element() Laurent Vivier
2026-03-02  0:54   ` David Gibson
2026-02-27 14:03 ` [PATCH 10/12] vu_common: Accept explicit iovec count per element in vu_init_elem() Laurent Vivier
2026-03-02  0:55   ` David Gibson
2026-02-27 14:03 ` [PATCH 11/12] vu_common: Prepare to use multibuffer with guest RX Laurent Vivier
2026-03-02  0:59   ` David Gibson
2026-02-27 14:03 ` [PATCH 12/12] vhost-user,udp: Use 2 iovec entries per element Laurent Vivier
2026-03-02  1:03   ` David Gibson

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=20260227140330.2216753-1-lvivier@redhat.com \
    --to=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).