public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Laurent Vivier <lvivier@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v10 30/30] packet: Add support for multi-vector packets
Date: Fri, 15 Aug 2025 11:11:37 +1000	[thread overview]
Message-ID: <aJ6JScoHACqf6s2B@zatzit> (raw)
In-Reply-To: <20250814094849.919709-31-lvivier@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2625 bytes --]

On Thu, Aug 14, 2025 at 11:48:49AM +0200, Laurent Vivier wrote:
> The packet pool was previously limited to handling packets contained
> within a single buffer.
> 
> This patch extends the packet pool to support iovec array,
> allowing a single logical packet to be composed of multiple iovec.
> 
> To accommodate this, the storage format within the pool is modified.
> For a multi-vector packet, a header entry is now stored first with
> iov_base = NULL and iov_len holding the number of subsequent
> vectors. The actual data vectors are then stored in the following
> pool slots.
> 
> The packet_add_do() and packet_get_do() functions are updated to
> manage this new format for storing and retrieving packets. The
> pool_full() check is also adjusted to ensure there is enough
> space for all vectors of a new packet before adding it.
> 
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> ---
>  packet.c | 52 ++++++++++++++++++++++++++++++++++------------------
>  packet.h |  2 +-
>  tap.c    |  4 ++--
>  3 files changed, 37 insertions(+), 21 deletions(-)
> 
> diff --git a/packet.c b/packet.c
> index 27693c55a138..c88e726c94a6 100644
> --- a/packet.c
> +++ b/packet.c
> @@ -91,14 +91,15 @@ static int packet_check_range(const struct pool *p, const char *ptr, size_t len,
>  	return 0;
>  }
>  /**
> - * pool_full() - Is a packet pool full?
> + * pool_can_fit() - Is a new packet can fit in the pool?

"Can a new packet fit in the pool?"

>   * @p:		Pointer to packet pool
> + * @data:	check data can fit in the pool
>   *
> - * Return: true if the pool is full, false if more packets can be added
> + * Return: true if the pool is full, false if data can be added

With the name changed, the sense needs to be inverted as well.  Also
s/data/@data/ to make it clear we're talking specifically about the
parameter, not "data" in the broad sense.

>   */
> -bool pool_full(const struct pool *p)
> +bool pool_can_fit(const struct pool *p, const struct iov_tail *data)
>  {
> -	return p->count >= p->size;
> +	return p->count + data->cnt  + (data->cnt > 1) >= p->size;

Still an off-by-one here, see comments in the other thread.

..and this is still only valid if @data is already pruned.  I really
think a bunch of things would become a bit clearer if you add a change
earlier in the series clarifying that iov_tails should never be passed
around unpruned.

-- 
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 --]

      reply	other threads:[~2025-08-15  1:11 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14  9:48 [PATCH v10 00/30] Introduce discontiguous frames management Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 01/30] arp: Don't mix incoming and outgoing buffers Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 02/30] iov: Introduce iov_tail_clone() and iov_drop_header() Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 03/30] iov: Update IOV_REMOVE_HEADER() and IOV_PEEK_HEADER() Laurent Vivier
2025-08-15  1:01   ` David Gibson
2025-08-14  9:48 ` [PATCH v10 04/30] tap: Use iov_tail with tap_add_packet() Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 05/30] packet: Use iov_tail with packet_add() Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 06/30] packet: Add packet_data() Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 07/30] arp: Convert to iov_tail Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 08/30] ndp: " Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 09/30] icmp: " Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 10/30] udp: " Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 11/30] tcp: Convert tcp_tap_handler() to use iov_tail Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 12/30] tcp: Convert tcp_data_from_tap() " Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 13/30] dhcpv6: move offset initialization out of dhcpv6_opt() Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 14/30] dhcpv6: Extract sending of NotOnLink status Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 15/30] dhcpv6: Convert to iov_tail Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 16/30] dhcpv6: Use iov_tail in dhcpv6_opt() Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 17/30] dhcp: Convert to iov_tail Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 18/30] ip: Use iov_tail in ipv6_l4hdr() Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 19/30] tap: Convert tap4_handler() to iov_tail Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 20/30] tap: Convert tap6_handler() " Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 21/30] packet: rename packet_data() to packet_get() Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 22/30] arp: use iov_tail rather than pool Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 23/30] dhcp: " Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 24/30] dhcpv6: " Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 25/30] icmp: " Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 26/30] ndp: " Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 27/30] packet: remove PACKET_POOL() and PACKET_POOL_P() Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 28/30] packet: remove unused parameter from PACKET_POOL_DECL() Laurent Vivier
2025-08-15  1:02   ` David Gibson
2025-08-14  9:48 ` [PATCH v10 29/30] packet: Refactor vhost-user memory region handling Laurent Vivier
2025-08-14  9:48 ` [PATCH v10 30/30] packet: Add support for multi-vector packets Laurent Vivier
2025-08-15  1:11   ` David Gibson [this message]

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=aJ6JScoHACqf6s2B@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).