From: David Gibson <david@gibson.dropbear.id.au>
To: Laurent Vivier <lvivier@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 05/12] iov: Add IOV_PUT_HEADER() to write header data back to iov_tail
Date: Mon, 2 Mar 2026 11:08:45 +1100 [thread overview]
Message-ID: <aaTVDcVRD1OyLMTW@zatzit> (raw)
In-Reply-To: <20260227140330.2216753-6-lvivier@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3735 bytes --]
On Fri, Feb 27, 2026 at 03:03:23PM +0100, Laurent Vivier wrote:
> Add a counterpart to IOV_PEEK_HEADER() that writes header data back
> to an iov_tail after modification. If the header pointer matches the
> original iov buffer location, it only advances the offset. Otherwise,
> it copies the data using iov_from_buf().
>
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
Concept looks good to me.
> ---
> iov.c | 22 ++++++++++++++++++++++
> iov.h | 14 +++++++++++++-
> 2 files changed, 35 insertions(+), 1 deletion(-)
>
> diff --git a/iov.c b/iov.c
> index 8836305fb701..2cf23d284e4a 100644
> --- a/iov.c
> +++ b/iov.c
> @@ -296,6 +296,28 @@ void *iov_peek_header_(struct iov_tail *tail, void *v, size_t len, size_t align)
> return v;
> }
>
> +/**
> + * iov_put_header_() - Write header back to an IOV tail
> + * @tail: IOV tail to write header to
> + * @v: Pointer to header data to write
> + * @len: Length of header to write, in bytes
> + *
> + * Return: number of bytes written
> + */
> +/* cppcheck-suppress unusedFunction */
> +size_t iov_put_header_(struct iov_tail *tail, const void *v, size_t len)
> +{
> + size_t l = len;
> +
> + /* iov_peek_header_() already called iov_check_header() */
> + if ((char *)tail->iov[0].iov_base + tail->off != v)
> + l = iov_from_buf(tail->iov, tail->cnt, tail->off, v, len);
IIUC, there's a strong requirement that this only be called after a
matching iov_peek_header_(), yes? If that's the case then (l != len)
would mean something has already gone badly wrong - so should it be an
ASSERT()?
> + tail->off += l;
> +
> + return l;
> +}
> +
> /**
> * iov_remove_header_() - Remove a header from an IOV tail
> * @tail: IOV tail to remove header from (modified)
> diff --git a/iov.h b/iov.h
> index a7b873d58134..08cf60639358 100644
> --- a/iov.h
> +++ b/iov.h
> @@ -86,6 +86,7 @@ bool iov_tail_prune(struct iov_tail *tail);
> size_t iov_tail_size(struct iov_tail *tail);
> bool iov_drop_header(struct iov_tail *tail, size_t len);
> void *iov_peek_header_(struct iov_tail *tail, void *v, size_t len, size_t align);
> +size_t iov_put_header_(struct iov_tail *tail, const void *v, size_t len);
> void *iov_remove_header_(struct iov_tail *tail, void *v, size_t len, size_t align);
> ssize_t iov_tail_clone(struct iovec *dst_iov, size_t dst_iov_cnt,
> struct iov_tail *tail);
> @@ -110,6 +111,16 @@ void iov_tail_zero_end(struct iov_tail *tail, size_t size);
> sizeof(var_), \
> __alignof__(var_))))
>
> +/**
> + * IOV_PUT_HEADER() - Write header back to an IOV tail
> + * @tail_: IOV tail to write header to
> + * @var_: Pointer to a variable containing the header data to write
> + *
> + * Return: number of bytes written
> + */
> +#define IOV_PUT_HEADER(tail_, var_) \
> + (iov_put_header_((tail_), (var_), sizeof(*var_)))
> +
> /**
> * IOV_REMOVE_HEADER() - Remove and return typed header from an IOV tail
> * @tail_: IOV tail to remove header from (modified)
> @@ -128,7 +139,8 @@ void iov_tail_zero_end(struct iov_tail *tail, size_t size);
> ((__typeof__(var_) *)(iov_remove_header_((tail_), &(var_), \
> sizeof(var_), __alignof__(var_))))
>
> -/** IOV_DROP_HEADER() - Remove a typed header from an IOV tail
> +/**
> + * IOV_DROP_HEADER() - Remove a typed header from an IOV tail
> * @tail_: IOV tail to remove header from (modified)
> * @type_: Data type of the header to remove
> *
> --
> 2.53.0
>
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-03-02 0:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 14:03 [PATCH 00/12] vhost-user,udp: Handle multiple iovec entries per virtqueue element Laurent Vivier
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 [this message]
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=aaTVDcVRD1OyLMTW@zatzit \
--to=david@gibson.dropbear.id.au \
--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).