From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top, Laurent Vivier <lvivier@redhat.com>
Subject: Re: [PATCH] ip: Use regular htons() for non-constant protocol number in L2_BUF_IP4_PSUM
Date: Fri, 8 Mar 2024 11:55:32 +1100 [thread overview]
Message-ID: <ZepiBI6HZvglkzQB@zatzit> (raw)
In-Reply-To: <20240306070836.3417504-1-sbrivio@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1833 bytes --]
On Wed, Mar 06, 2024 at 08:08:36AM +0100, Stefano Brivio wrote:
> instead of htons_constant(), which is for... constants.
>
> Fixes: 5bf200ae8a1a ("tcp, udp: Don't include destination address in partially precomputed csums")
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
It seems to get the job done, at what's probably negligible practical
cost. My perfectionist side has some misgivings:
AIUI, the point of htons_constant() isn't so much that it *requires* a
constant, but that because it's open-coded in plain arithmetic
operations the compiler will be able to constant fold it, if it is
invoked with a constant parameter. Since htons() is a library
function, it probably can't be elided in that way. The cost of
htons_constant() is that it may be a less optimal implementation when
the calculation really does need to be done at runtime.
I'm still a bit baffled at that Coverity warning: I can't see why it
doesn't preclude any situation where you want to write out
calculations for clarity, even though you know the result will be a
constant (and you expect the compiler to fold it).
> ---
> ip.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/ip.h b/ip.h
> index 9be4778..b9aedf6 100644
> --- a/ip.h
> +++ b/ip.h
> @@ -38,7 +38,7 @@
> .daddr = 0, \
> }
> #define L2_BUF_IP4_PSUM(proto) ((uint32_t)htons_constant(0x4500) + \
> - (uint32_t)htons_constant(0xff00 | (proto)))
> + (uint32_t)htons(0xff00 | (proto)))
>
> #define L2_BUF_IP6_INIT(proto) \
> { \
--
David Gibson | 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 --]
next prev parent reply other threads:[~2024-03-08 1:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 7:08 [PATCH] ip: Use regular htons() for non-constant protocol number in L2_BUF_IP4_PSUM Stefano Brivio
2024-03-08 0:55 ` David Gibson [this message]
2024-03-08 9:28 ` Stefano Brivio
2024-03-14 5:02 ` David Gibson
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=ZepiBI6HZvglkzQB@zatzit \
--to=david@gibson.dropbear.id.au \
--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).