bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>
Subject: Re: [PATCH v2 bpf-next] bpf: improve the general precision of tnum_mul
Date: Mon, 18 Aug 2025 15:47:22 -0700	[thread overview]
Message-ID: <1cb633fd44d74459d2ac0bb84fe0233d56b76242.camel@gmail.com> (raw)
In-Reply-To: <e9549198-f0d6-466d-a104-99b228d35dde@nandakumar.co.in>

On Sat, 2025-08-16 at 10:28 +0530, Nandakumar Edamana wrote:

[...]

> mine vs kernel (bits = 6):
>    better = 285059
>    same   = 229058
>    worse  = 17324

Did you found any patterns for cases where new algorithm fairs worse
compared to current?

[...]

  parent reply	other threads:[~2025-08-18 22:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15 14:05 [PATCH v2 bpf-next] bpf: improve the general precision of tnum_mul Nandakumar Edamana
2025-08-15 19:10 ` Eduard Zingerman
2025-08-16  4:58   ` Nandakumar Edamana
2025-08-18 22:16     ` Eduard Zingerman
2025-08-18 22:47     ` Eduard Zingerman [this message]
2025-08-18 14:24   ` Daniel Borkmann
2025-08-20  6:15   ` Harishankar Vishwanathan
     [not found]     ` <0ba41cd7-adc0-4c65-b1e0-defd8ebc2d64@nandakumar.co.in>
2025-08-20  7:48       ` Fwd: " Nandakumar Edamana
2025-08-21  5:46         ` Harishankar Vishwanathan
2025-08-20 10:31       ` Nandakumar Edamana
2025-08-18 18:23 ` Jakub Sitnicki
2025-08-18 22:49   ` Eduard Zingerman
2025-08-19  9:20     ` Jakub Sitnicki
2025-08-29  4:04       ` Shung-Hsi Yu
2025-08-18 23:14 ` Eduard Zingerman
     [not found]   ` <3b7b2ed1-bce1-49da-b83c-2ca46850062c@nandakumar.co.in>
2025-08-18 23:31     ` Eduard Zingerman

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=1cb633fd44d74459d2ac0bb84fe0233d56b76242.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=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).