public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 02/10] iov: Add iov_memcopy() to copy data between iovec arrays
Date: Fri, 03 Apr 2026 08:20:18 +0200 (CEST)	[thread overview]
Message-ID: <20260403082017.0b91aa2c@elisabeth> (raw)
In-Reply-To: <20260401191826.1782394-3-lvivier@redhat.com>

Nits, all about names:

On Wed,  1 Apr 2026 21:18:18 +0200
Laurent Vivier <lvivier@redhat.com> wrote:

> Add a helper to copy data from a source iovec array to a destination
> iovec array, each starting at an arbitrary byte offset, iterating
> through both arrays simultaneously and copying in chunks matching the
> smaller of the two current segments.
> 
> 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 0188acdf5eba..83b683f3976a 100644
> --- a/iov.c
> +++ b/iov.c
> @@ -197,6 +197,58 @@ void iov_memset(const struct iovec *iov, size_t iov_cnt, size_t offset, int c,
>  	}
>  }
>  
> +/**
> + * iov_memcopy() - Copy data between two iovec arrays

Wouldn't it be less surprising to call this iov_memcpy(), like memcpy()?

> + * @dst_iov:		Destination iovec array
> + * @dst_iov_cnt:	Number of elements in destination iovec array
> + * @dst_offs:		Destination offset
> + * @iov:		Source iovec array
> + * @iov_cnt:		Number of elements in source iovec array

I think @src_iov and @src_iov_cnt would make the whole function easier
to follow and look more symmetric.

> + * @offs:		Source offset

What about @dst_offset and @src_offset? "offs" as a short-form for
"offset" isn't really obvious (to me at least).

> + * @length:		Number of bytes to copy
> + *
> + * Return: total number of bytes copied
> + */
> +/* cppcheck-suppress unusedFunction */
> +size_t iov_memcopy(struct iovec *dst_iov, size_t dst_iov_cnt, size_t dst_offs,
> +		   const struct iovec *iov, size_t iov_cnt, size_t offs,
> +		   size_t length)
> +{
> +	unsigned int i, j;
> +	size_t total = 0;
> +
> +	i = iov_skip_bytes(iov, iov_cnt, offs, &offs);
> +	j = iov_skip_bytes(dst_iov, dst_iov_cnt, dst_offs, &dst_offs);
> +
> +	/* copying data */
> +	while (length && i < iov_cnt && j < dst_iov_cnt) {
> +		size_t n = MIN(dst_iov[j].iov_len - dst_offs,
> +			       iov[i].iov_len - offs);
> +
> +		if (n > length)
> +			n = length;
> +
> +		memcpy((char *)dst_iov[j].iov_base + dst_offs,
> +		       (const char *)iov[i].iov_base + offs, n);
> +
> +		dst_offs += n;
> +		offs += n;
> +		total += n;
> +		length -= n;
> +
> +		if (dst_offs == dst_iov[j].iov_len) {
> +			dst_offs = 0;
> +			j++;
> +		}
> +		if (offs == iov[i].iov_len) {
> +			offs = 0;
> +			i++;
> +		}
> +	}
> +
> +	return total;
> +}
> +
>  /**
>   * iov_tail_prune() - Remove any unneeded buffers from an IOV tail
>   * @tail:	IO vector tail (modified)
> diff --git a/iov.h b/iov.h
> index d295d05b3bab..074266e127ef 100644
> --- a/iov.h
> +++ b/iov.h
> @@ -32,6 +32,9 @@ size_t iov_size(const struct iovec *iov, size_t iov_cnt);
>  size_t iov_truncate(struct iovec *iov, size_t iov_cnt, size_t size);
>  void iov_memset(const struct iovec *iov, size_t iov_cnt, size_t offset, int c,
>  		size_t length);
> +size_t iov_memcopy(struct iovec *dst_iov, size_t dst_iov_cnt, size_t dst_offs,
> +		   const struct iovec *iov, size_t iov_cnt, size_t offs,
> +		   size_t length);
>  
>  /*
>   * DOC: Theory of Operation, struct iov_tail

-- 
Stefano


  reply	other threads:[~2026-04-03  6:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01 19:18 [PATCH 00/10] vhost-user: Preparatory series for multiple iovec entries per virtqueue element Laurent Vivier
2026-04-01 19:18 ` [PATCH 01/10] iov: Introduce iov_memset() Laurent Vivier
2026-04-03 12:35   ` David Gibson
2026-04-01 19:18 ` [PATCH 02/10] iov: Add iov_memcopy() to copy data between iovec arrays Laurent Vivier
2026-04-03  6:20   ` Stefano Brivio [this message]
2026-04-01 19:18 ` [PATCH 03/10] vu_common: Move vnethdr setup into vu_flush() Laurent Vivier
2026-04-03  6:20   ` Stefano Brivio
2026-04-03 10:16     ` Laurent Vivier
2026-04-01 19:18 ` [PATCH 04/10] udp_vu: Move virtqueue management from udp_vu_sock_recv() to its caller Laurent Vivier
2026-04-01 19:18 ` [PATCH 05/10] udp_vu: Pass iov explicitly to helpers instead of using file-scoped array Laurent Vivier
2026-04-01 19:18 ` [PATCH 06/10] checksum: Pass explicit L4 length to checksum functions Laurent Vivier
2026-04-01 19:18 ` [PATCH 07/10] pcap: Pass explicit L2 length to pcap_iov() Laurent Vivier
2026-04-03  6:20   ` Stefano Brivio
2026-04-03 10:19     ` Laurent Vivier
2026-04-01 19:18 ` [PATCH 08/10] vu_common: Pass explicit frame length to vu_flush() Laurent Vivier
2026-04-03  6:20   ` Stefano Brivio
2026-04-01 19:18 ` [PATCH 09/10] tcp: Pass explicit data length to tcp_fill_headers() Laurent Vivier
2026-04-01 19:18 ` [PATCH 10/10] vhost-user: Centralise Ethernet frame padding in vu_collect() and vu_pad() Laurent Vivier
2026-04-03  6:20   ` Stefano Brivio
2026-04-03 10:25     ` 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=20260403082017.0b91aa2c@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).