From: Laurent Vivier <lvivier@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v2 06/13] iov: Add IOV_PUT_HEADER() to write header data back to iov_tail
Date: Thu, 12 Mar 2026 09:20:15 +0100 [thread overview]
Message-ID: <3c6851e3-247c-46fb-81f4-dcb2a39a5df8@redhat.com> (raw)
In-Reply-To: <abI9EFqgsp0_aeXu@zatzit>
On 3/12/26 05:12, David Gibson wrote:
> On Mon, Mar 09, 2026 at 10:47:37AM +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>
>
> Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
>
> Although a couple of thoughts on possible improvements below.
>
>> ---
>> iov.c | 24 ++++++++++++++++++++++++
>> iov.h | 14 +++++++++++++-
>> 2 files changed, 37 insertions(+), 1 deletion(-)
>>
>> diff --git a/iov.c b/iov.c
>> index cd48667226f3..296f24b61067 100644
>> --- a/iov.c
>> +++ b/iov.c
>> @@ -305,6 +305,30 @@ 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);
>
> This assumes the tail is already pruned. That will be the case
> assuming this has a matching iov_peek_header_(), but it might be
> better to explicitly document that assumption.
>
> Better yet, is there a way we could enforce these come in pairs.
> Something like:
>
> struct some_header *hdr;
>
> with_header(hdr, tail) {
> hdr->a = 123;
> hdr->b = hdr->c - 7;
> }
>
> Where,
> #define with_header(hdr, tail)
> for ((typeof *(hdr)) store, hdr = IOV_PEEK_HEADER(tail, store);
> hdr;
> IOV_PUT_HEADER(tail, hdr), hdr = NULL)
>
I really like the idea.
Thanks,
Laurent
next prev parent reply other threads:[~2026-03-12 8:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 9:47 [PATCH v2 00/13] vhost-user,udp: Handle multiple iovec entries per virtqueue element Laurent Vivier
2026-03-09 9:47 ` [PATCH v2 01/13] iov: Add iov_truncate() helper and use it in vu handlers Laurent Vivier
2026-03-09 9:47 ` [PATCH v2 02/13] vhost-user: Centralise 802.3 frame padding in vu_collect() and vu_flush() Laurent Vivier
2026-03-12 2:05 ` David Gibson
2026-03-09 9:47 ` [PATCH v2 03/13] vhost-user: Use ARRAY_SIZE(elem) instead of VIRTQUEUE_MAX_SIZE Laurent Vivier
2026-03-09 9:47 ` [PATCH v2 04/13] udp_vu: Use iov_tail to manage virtqueue buffers Laurent Vivier
2026-03-12 2:38 ` David Gibson
2026-03-09 9:47 ` [PATCH v2 05/13] udp_vu: Move virtqueue management from udp_vu_sock_recv() to its caller Laurent Vivier
2026-03-12 3:44 ` David Gibson
2026-03-09 9:47 ` [PATCH v2 06/13] iov: Add IOV_PUT_HEADER() to write header data back to iov_tail Laurent Vivier
2026-03-12 4:12 ` David Gibson
2026-03-12 8:20 ` Laurent Vivier [this message]
2026-03-09 9:47 ` [PATCH v2 07/13] udp: Pass iov_tail to udp_update_hdr4()/udp_update_hdr6() Laurent Vivier
2026-03-12 4:16 ` David Gibson
2026-03-09 9:47 ` [PATCH v2 08/13] udp_vu: Use iov_tail in udp_vu_prepare() Laurent Vivier
2026-03-12 4:30 ` David Gibson
2026-03-12 8:19 ` Laurent Vivier
2026-03-12 9:51 ` David Gibson
2026-03-09 9:47 ` [PATCH v2 09/13] vu_common: Pass iov_tail to vu_set_vnethdr() Laurent Vivier
2026-03-12 4:34 ` David Gibson
2026-03-09 9:47 ` [PATCH v2 10/13] vu_common: Accept explicit iovec counts in vu_set_element() Laurent Vivier
2026-03-09 9:47 ` [PATCH v2 11/13] vu_common: Accept explicit iovec count per element in vu_init_elem() Laurent Vivier
2026-03-09 9:47 ` [PATCH v2 12/13] vu_common: Prepare to use multibuffer with guest RX Laurent Vivier
2026-03-09 9:47 ` [PATCH v2 13/13] vhost-user,udp: Use 2 iovec entries per element Laurent Vivier
2026-03-12 4:39 ` David Gibson
2026-03-12 8:08 ` Laurent Vivier
2026-03-12 9:47 ` David Gibson
2026-03-12 10:42 ` Laurent Vivier
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=3c6851e3-247c-46fb-81f4-dcb2a39a5df8@redhat.com \
--to=lvivier@redhat.com \
--cc=david@gibson.dropbear.id.au \
--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).