From: Stefano Brivio <sbrivio@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v2 2/3] vu_handle_tx: Pass actual remaining out_sg capacity to vu_queue_pop()
Date: Tue, 17 Mar 2026 01:02:27 +0100 (CET) [thread overview]
Message-ID: <20260317010227.565ffb1c@elisabeth> (raw)
In-Reply-To: <20260313182618.4157365-3-lvivier@redhat.com>
On Fri, 13 Mar 2026 19:26:17 +0100
Laurent Vivier <lvivier@redhat.com> wrote:
> In vu_handle_tx(), pass the actual remaining iovec capacity
> (ARRAY_SIZE(out_sg) - out_sg_count) to vu_queue_pop() rather than a
> fixed VU_MAX_TX_BUFFER_NB.
>
> This enables dynamic allocation of iovec entries to each element rather
> than reserving a fixed number of slots per descriptor.
>
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> ---
> vu_common.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/vu_common.c b/vu_common.c
> index 4d809ac38a4b..ed0033d6bb11 100644
> --- a/vu_common.c
> +++ b/vu_common.c
> @@ -20,8 +20,6 @@
> #include "migrate.h"
> #include "epoll_ctl.h"
>
> -#define VU_MAX_TX_BUFFER_NB 2
> -
> /**
> * vu_packet_check_range() - Check if a given memory zone is contained in
> * a mapped guest memory region
> @@ -177,13 +175,14 @@ static void vu_handle_tx(struct vu_dev *vdev, int index,
>
> count = 0;
> out_sg_count = 0;
> - while (count < VIRTQUEUE_MAX_SIZE &&
> - out_sg_count + VU_MAX_TX_BUFFER_NB <= VIRTQUEUE_MAX_SIZE) {
> - int ret;
> + while (count < ARRAY_SIZE(elem) &&
> + out_sg_count < ARRAY_SIZE(out_sg)) {
Nit: you could do this now:
while (count < ARRAY_SIZE(elem) && out_sg_count < ARRAY_SIZE(out_sg)) {
I still need a bit of time to review 3/3, if you don't need to re-spin
for other reasons I can also fix this up on merge.
> struct iov_tail data;
> + int ret;
>
> ret = vu_queue_pop(vdev, vq, &elem[count], NULL, 0,
> - &out_sg[out_sg_count], VU_MAX_TX_BUFFER_NB);
> + &out_sg[out_sg_count],
> + ARRAY_SIZE(out_sg) - out_sg_count);
> if (ret < 0)
> break;
> out_sg_count += elem[count].out_num;
--
Stefano
next prev parent reply other threads:[~2026-03-17 0:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 18:26 [PATCH v2 0/3] Decouple iovec management from virtqueue elements Laurent Vivier
2026-03-13 18:26 ` [PATCH v2 1/3] virtio: Pass iovec arrays as separate parameters to vu_queue_pop() Laurent Vivier
2026-03-16 8:25 ` David Gibson
2026-03-13 18:26 ` [PATCH v2 2/3] vu_handle_tx: Pass actual remaining out_sg capacity " Laurent Vivier
2026-03-16 9:15 ` David Gibson
2026-03-17 0:02 ` Stefano Brivio [this message]
2026-03-13 18:26 ` [PATCH v2 3/3] vu_common: Move iovec management into vu_collect() Laurent Vivier
2026-03-17 2:40 ` David Gibson
2026-03-17 7:25 ` Laurent Vivier
2026-03-17 15:23 ` Stefano Brivio
2026-03-17 15:23 ` Stefano Brivio
2026-03-17 16:18 ` Laurent Vivier
2026-03-17 16:21 ` Stefano Brivio
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=20260317010227.565ffb1c@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).