[PATCH v5 0/4] vhost-user,tcp: Handle multiple iovec entries per virtqueue element

[Laurent Vivier <lvivier@redhat.com>]

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: 20260403164241.3212528-1-lvivier@redhat.com

v5:
- Use l2len variable for pcap_iov() length in tcp_vu_send_flag()
- Add braces
- Move pcap_iov() before vu_flush()
- Remove vu_flush() from tcp_vu_send_dup(), let the caller handle it

v4:
- fix error during rebasei, s/vu_pad_len/vu_pad/

v3:
- Rebased on top of
  [PATCH 00/10] vhost-user: Preparatory series for multiple iovec entries per virtqueue element

v2:
- add "tcp: Encode checksum computation flags in a single parameter"
- remove IOV_PUT_HEADER()/with_header() and use IOV_PUSH_HEADER()
- don't use the iov_tail to provide the headers to the functions

Laurent Vivier (4):
  tcp: Encode checksum computation flags in a single parameter
  tcp_vu: Build headers on the stack and write them into the iovec
  tcp_vu: Support multibuffer frames in tcp_vu_sock_recv()
  tcp_vu: Support multibuffer frames in tcp_vu_send_flag()

 iov.c          |   1 -
 tcp.c          |  25 +--
 tcp_buf.c      |  23 +--
 tcp_internal.h |   7 +-
 tcp_vu.c       | 403 +++++++++++++++++++++++++++++--------------------
 vu_common.h    |  20 ---
 6 files changed, 270 insertions(+), 209 deletions(-)

-- 
2.53.0