From: Eduard Zingerman <eddyz87@gmail.com>
To: Nandakumar Edamana <nandakumar@nandakumar.co.in>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Jakub Sitnicki <jakub@cloudflare.com>,
Harishankar Vishwanathan <harishankar.vishwanathan@gmail.com>
Subject: Re: [PATCH v4 bpf-next 1/2] bpf: improve the general precision of tnum_mul
Date: Fri, 22 Aug 2025 16:56:12 -0700 [thread overview]
Message-ID: <0ed1ad1d73d2c4468b3a02b3034b7dfd6e693d66.camel@gmail.com> (raw)
In-Reply-To: <116ef3d2-51a5-444c-ad51-126043649226@nandakumar.co.in>
On Sat, 2025-08-23 at 05:18 +0530, Nandakumar Edamana wrote:
[...]
> I personally don't think `best(a*b, b*a)` is ugly. What about
> `best(oldprod, newprod)`, where oldprod and newprod are each found
> like this, using the old tnum_mul and the new tnum_mul respectively?
Hm, given that both are correct if we go for a hybrid approach we can
peek known bits from both.
next prev parent reply other threads:[~2025-08-22 23:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 17:08 [PATCH v4 bpf-next 1/2] bpf: improve the general precision of tnum_mul Nandakumar Edamana
2025-08-22 17:08 ` [PATCH v4 bpf-next 2/2] bpf: add selftest to check the verifier's abstract multiplication Nandakumar Edamana
2025-08-22 18:59 ` Eduard Zingerman
2025-08-22 18:37 ` [PATCH v4 bpf-next 1/2] bpf: improve the general precision of tnum_mul Eduard Zingerman
2025-08-22 18:58 ` Nandakumar Edamana
2025-08-22 21:14 ` Harishankar Vishwanathan
2025-08-22 21:50 ` Eduard Zingerman
2025-08-22 23:48 ` Nandakumar Edamana
2025-08-22 23:56 ` Eduard Zingerman [this message]
2025-08-25 4:16 ` Nandakumar Edamana
2025-08-25 16:24 ` Eduard Zingerman
2025-08-25 16:56 ` Nandakumar Edamana
2025-08-25 16:57 ` Eduard Zingerman
2025-08-25 15:51 ` Eduard Zingerman
2025-08-22 23:50 ` Harishankar Vishwanathan
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=0ed1ad1d73d2c4468b3a02b3034b7dfd6e693d66.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=harishankar.vishwanathan@gmail.com \
--cc=jakub@cloudflare.com \
--cc=nandakumar@nandakumar.co.in \
/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.
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 NNTP newsgroup(s).