From: Laurent Vivier <laurent@vivier.eu>
To: Stefano Brivio <sbrivio@redhat.com>, Laurent Vivier <lvivier@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH trivial] tcp_vu, udp_vu: Fix comment headers for header length functions
Date: Tue, 24 Feb 2026 16:26:59 +0100 [thread overview]
Message-ID: <a887cb7f-ef55-48e2-844e-375de239da13@vivier.eu> (raw)
In-Reply-To: <20260224162409.6ab5eb90@elisabeth>
On 2/24/26 16:24, Stefano Brivio wrote:
> On Tue, 24 Feb 2026 13:22:27 +0100
> Laurent Vivier <lvivier@redhat.com> wrote:
>
>> The comment headers for tcp_vu_hdrlen() and udp_vu_hdrlen() described
>> the return value as "the size of the header in level 2 frame", but
>> these functions also include the virtio net header, which is not part
>> of the L2 frame.
>>
>> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
>> ---
>> tcp_vu.c | 4 ++--
>> udp_vu.c | 4 ++--
>> 2 files changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/tcp_vu.c b/tcp_vu.c
>> index 94169c21f700..8908d376a7dd 100644
>> --- a/tcp_vu.c
>> +++ b/tcp_vu.c
>> @@ -40,10 +40,10 @@ static struct vu_virtq_element elem[VIRTQUEUE_MAX_SIZE];
>> static int head[VIRTQUEUE_MAX_SIZE + 1];
>>
>> /**
>> - * tcp_vu_hdrlen() - return the size of the header in level 2 frame (TCP)
>> + * tcp_vu_hdrlen() - Return the size of virtio net and L2 headers (TCP)
>
> Thanks, I think that this, plus the line changed below, makes it clear.
>
> What I still find confusing is: "L2 headers (TCP)". If I see this
> together with udp_vu_hdrlen() I understand what you mean, but
> otherwise I'd ask myself what TCP has to do with Layer-2...
>
> I tried rephrasing it a bit, what do you think about:
>
> * tcp_vu_hdrlen() - Sum size of all headers, from TCP to virtio-net
>
>> * @v6: Set for IPv6 packet
>> *
>> - * Return: return the size of the header
>> + * Return: total size of virtio net header, Ethernet, IP and TCP headers
>
> ...and changing this to "virtio-net" (not a very official name but it
> seems to be widely used, more than "virtio net"...)?
>
> If you're fine with it (same for UDP) I would change it and apply. I'm
> not exactly proud of this either, so if you or somebody else has better
> ideas...
I'm fine with it, go ahead...
Thanks,
Laurent
next prev parent reply other threads:[~2026-02-24 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 12:22 Laurent Vivier
2026-02-24 15:24 ` Stefano Brivio
2026-02-24 15:26 ` Laurent Vivier [this message]
2026-02-24 17:57 ` 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=a887cb7f-ef55-48e2-844e-375de239da13@vivier.eu \
--to=laurent@vivier.eu \
--cc=lvivier@redhat.com \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.com \
/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).