From: Stefano Brivio <sbrivio@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v6 02/30] iov: Introduce iov_tail_clone() and iov_tail_drop().
Date: Wed, 11 Jun 2025 14:52:12 +0200 [thread overview]
Message-ID: <20250611145212.75ed7fe6@elisabeth> (raw)
In-Reply-To: <20250604130834.3868010-3-lvivier@redhat.com>
On Wed, 4 Jun 2025 15:08:06 +0200
Laurent Vivier <lvivier@redhat.com> wrote:
> These utilities enhance iov_tail manipulation, useful for
> efficient packet processing by enabling iovec array cloning and
> header stripping without data copies.
>
> - iov_tail_drop(): Discards a specified number of bytes from the
> beginning of an iov_tail by advancing its internal offset and pruning
> consumed elements.
>
> - iov_tail_clone(): Clone an iov_tail into an iovec array, adjusting the
> first iovec entry to remove the iov_tail offset.
>
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> ---
> iov.c | 52 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> iov.h | 3 +++
> 2 files changed, 55 insertions(+)
>
> diff --git a/iov.c b/iov.c
> index 91e87a740f0a..3b89f8126ee7 100644
> --- a/iov.c
> +++ b/iov.c
> @@ -192,6 +192,21 @@ size_t iov_tail_size(struct iov_tail *tail)
> return iov_size(tail->iov, tail->cnt) - tail->off;
> }
>
> +/**
> + * iov_tail_drop() - Discard a header from an IOV tail
Same as v5:
---
On Mon, 26 May 2025 16:19:03 +0200
Stefano Brivio <sbrivio@redhat.com> wrote:
> Mixing 'header' with 'tail' makes this a bit confusing. Yes, these
> vectors are used for headers, but what about calling it simply 'item',
> to match the context of this function?
---
> + * @tail: IO vector tail
> + * @len: length to move the head of the tail
> + *
> + * Returns: true if the item still contains any bytes, otherwise false
Nit: we always use the imperative mood here, and no tabs, "Return: true
if...".
> + */
> +/* cppcheck-suppress unusedFunction */
> +bool iov_tail_drop(struct iov_tail *tail, size_t len)
> +{
> + tail->off = tail->off + len;
> +
> + return iov_tail_prune(tail);
> +}
> +
> /**
> * iov_peek_header_() - Get pointer to a header from an IOV tail
> * @tail: IOV tail to get header from
> @@ -248,3 +263,40 @@ void *iov_remove_header_(struct iov_tail *tail, size_t len, size_t align)
> tail->off = tail->off + len;
> return p;
> }
> +
> +/**
> + * iov_tail_clone() - Assign iov references referencing a subset of the data
Nit (same as for iov_slice() in v5): "iov_tail_clone() - Assign ..."
> + * in an iov_tail
> + *
> + * @dst_iov: Pointer to the destination array of struct iovec describing
> + * the scatter/gather I/O vector to copy to.
Same as v5: perhaps "...to shallow copy to"?
> + * @dst_iov_cnt: Maximum number of elements in the destination iov array.
> + * @tail: Pointer to the source iov_tail
> + *
> + * Returns: The number of elements successfully copied to the destination
"referenced from the destination iov array"?
Same as above: "Return: the number of..."
> + * iov array, a negative value if there is not enough room in the
> + * destination iov array
> + */
> +/* cppcheck-suppress unusedFunction */
> +ssize_t iov_tail_clone(struct iovec *dst_iov, size_t dst_iov_cnt,
> + struct iov_tail *tail)
> +{
> + const struct iovec *iov = &tail->iov[0];
> + size_t iov_cnt = tail->cnt;
> + size_t offset = tail->off;
> + unsigned int i, j;
> +
> + i = iov_skip_bytes(iov, iov_cnt, offset, &offset);
> +
> + /* assign iov references referencing a subset of the source one */
Nit: excess whitespace.
> + for (j = 0; i < iov_cnt && j < dst_iov_cnt; i++, j++) {
> + dst_iov[j].iov_base = (char *)iov[i].iov_base + offset;
> + dst_iov[j].iov_len = iov[i].iov_len - offset;
> + offset = 0;
> + }
Nice, this is much less scary than the previous iov_slice().
> +
> + if (j == dst_iov_cnt && i != iov_cnt)
> + return -1;
> +
> + return j;
> +}
> diff --git a/iov.h b/iov.h
> index 9855bf0c0c32..11a8567aa183 100644
> --- a/iov.h
> +++ b/iov.h
> @@ -72,8 +72,11 @@ struct iov_tail {
>
> bool iov_tail_prune(struct iov_tail *tail);
> size_t iov_tail_size(struct iov_tail *tail);
> +bool iov_tail_drop(struct iov_tail *tail, size_t len);
> void *iov_peek_header_(struct iov_tail *tail, size_t len, size_t align);
> void *iov_remove_header_(struct iov_tail *tail, size_t len, size_t align);
> +ssize_t iov_tail_clone(struct iovec *dst_iov, size_t dst_iov_cnt,
> + struct iov_tail *tail);
>
> /**
> * IOV_PEEK_HEADER() - Get typed pointer to a header from an IOV tail
--
Stefano
next prev parent reply other threads:[~2025-06-11 12:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 13:08 [PATCH v6 00/30] Introduce discontiguous frames management Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 01/30] arp: Don't mix incoming and outgoing buffers Laurent Vivier
2025-06-11 12:52 ` Stefano Brivio
2025-06-04 13:08 ` [PATCH v6 02/30] iov: Introduce iov_tail_clone() and iov_tail_drop() Laurent Vivier
2025-06-11 12:52 ` Stefano Brivio [this message]
2025-06-04 13:08 ` [PATCH v6 03/30] iov: Update IOV_REMOVE_HEADER() and IOV_PEEK_HEADER() Laurent Vivier
2025-06-11 12:52 ` Stefano Brivio
2025-06-04 13:08 ` [PATCH v6 04/30] tap: Use iov_tail with tap_add_packet() Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 05/30] packet: Use iov_tail with packet_add() Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 06/30] packet: Add packet_data() Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 07/30] arp: Convert to iov_tail Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 08/30] ndp: " Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 09/30] icmp: " Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 10/30] udp: " Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 11/30] tcp: Convert tcp_tap_handler() to use iov_tail Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 12/30] tcp: Convert tcp_data_from_tap() " Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 13/30] dhcpv6: move offset initialization out of dhcpv6_opt() Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 14/30] dhcpv6: Extract sending of NotOnLink status Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 15/30] dhcpv6: Convert to iov_tail Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 16/30] dhcpv6: Use iov_tail in dhcpv6_opt() Laurent Vivier
2025-06-11 12:52 ` Stefano Brivio
2025-06-04 13:08 ` [PATCH v6 17/30] dhcp: Convert to iov_tail Laurent Vivier
2025-06-11 12:52 ` Stefano Brivio
2025-06-04 13:08 ` [PATCH v6 18/30] ip: Use iov_tail in ipv6_l4hdr() Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 19/30] tap: Convert tap4_handler() to iov_tail Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 20/30] tap: Convert tap6_handler() " Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 21/30] packet: rename packet_data() to packet_get() Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 22/30] arp: use iov_tail rather than pool Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 23/30] dhcp: " Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 24/30] dhcpv6: " Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 25/30] icmp: " Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 26/30] ndp: " Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 27/30] packet: remove PACKET_POOL() and PACKET_POOL_P() Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 28/30] packet: remove unused parameter from PACKET_POOL_DECL() Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 29/30] packet: add memory regions information into pool Laurent Vivier
2025-06-04 13:08 ` [PATCH v6 30/30] packet: use buf to store iovec array 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=20250611145212.75ed7fe6@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).