From: Eduard Zingerman <eddyz87@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Donglin Peng <dolinux.peng@gmail.com>
Cc: ast@kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, Alan Maguire <alan.maguire@oracle.com>,
Song Liu <song@kernel.org>, pengdonglin <pengdonglin@xiaomi.com>
Subject: Re: [RFC PATCH v4 1/7] libbpf: Extract BTF type remapping logic into helper function
Date: Tue, 04 Nov 2025 16:36:09 -0800 [thread overview]
Message-ID: <61e92756ea7f202f2e501747b574e97b2f5bc32f.camel@gmail.com> (raw)
In-Reply-To: <CAEf4BzaPDKJvQtCss4Gm1073wyBGXmixv4s9V5twnF7uEHRhPg@mail.gmail.com>
On Tue, 2025-11-04 at 16:11 -0800, Andrii Nakryiko wrote:
[...]
> > @@ -3400,6 +3400,37 @@ int btf_ext__set_endianness(struct btf_ext *btf_ext, enum btf_endianness endian)
> > return 0;
> > }
> >
> > +static int btf_remap_types(struct btf *btf, struct btf_ext *btf_ext,
> > + btf_remap_type_fn visit, void *ctx)
>
> tbh, my goal is to reduce the amount of callback usage within libbpf,
> not add more of it...
>
> I don't like this refactoring. We should convert
> btf_ext_visit_type_ids() into iterators, have btf_field_iter_init +
> btf_field_iter_next usable in for_each() form, and not try to reuse 5
> lines of code. See my comments in the next patch.
Remapping types is a concept.
I hate duplicating code for concepts.
Similarly, having patch #3 == patch #5 and patch #4 == patch #6 is
plain ugly. Just waiting for a bug because we changed the one but
forgot to change another in a year or two.
[...]
next prev parent reply other threads:[~2025-11-05 0:36 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 13:40 [RFC PATCH v4 0/7] libbpf: BTF performance optimizations with permutation and binary search Donglin Peng
2025-11-04 13:40 ` [RFC PATCH v4 1/7] libbpf: Extract BTF type remapping logic into helper function Donglin Peng
2025-11-04 23:16 ` Eduard Zingerman
2025-11-05 0:11 ` Andrii Nakryiko
2025-11-05 0:36 ` Eduard Zingerman [this message]
2025-11-05 0:57 ` Andrii Nakryiko
2025-11-05 1:23 ` Eduard Zingerman
2025-11-05 18:20 ` Andrii Nakryiko
2025-11-05 19:41 ` Eduard Zingerman
2025-11-06 17:09 ` Andrii Nakryiko
2025-11-04 13:40 ` [RFC PATCH v4 2/7] libbpf: Add BTF permutation support for type reordering Donglin Peng
2025-11-04 23:45 ` Eduard Zingerman
2025-11-05 11:31 ` Donglin Peng
2025-11-05 0:11 ` Andrii Nakryiko
2025-11-05 0:16 ` Eduard Zingerman
2025-11-05 1:04 ` Andrii Nakryiko
2025-11-05 1:20 ` Eduard Zingerman
2025-11-05 13:19 ` Donglin Peng
2025-11-05 18:32 ` Andrii Nakryiko
2025-11-05 18:23 ` Andrii Nakryiko
2025-11-05 19:23 ` Eduard Zingerman
2025-11-06 17:21 ` Andrii Nakryiko
2025-11-07 2:36 ` Donglin Peng
2025-11-07 17:43 ` Andrii Nakryiko
2025-11-05 12:52 ` Donglin Peng
2025-11-05 18:29 ` Andrii Nakryiko
2025-11-06 7:31 ` Donglin Peng
2025-11-06 17:12 ` Andrii Nakryiko
2025-11-07 1:39 ` Donglin Peng
2025-11-04 13:40 ` [RFC PATCH v4 3/7] libbpf: Optimize type lookup with binary search for sorted BTF Donglin Peng
2025-11-04 14:15 ` bot+bpf-ci
2025-11-05 0:06 ` Eduard Zingerman
2025-11-05 0:11 ` Andrii Nakryiko
2025-11-05 0:19 ` Eduard Zingerman
2025-11-05 0:54 ` Andrii Nakryiko
2025-11-05 1:17 ` Eduard Zingerman
2025-11-05 13:48 ` Donglin Peng
2025-11-05 16:52 ` Eduard Zingerman
2025-11-06 6:10 ` Donglin Peng
2025-11-05 18:11 ` Andrii Nakryiko
2025-11-06 7:49 ` Donglin Peng
2025-11-06 17:31 ` Andrii Nakryiko
2025-11-07 4:57 ` Donglin Peng
2025-11-07 17:01 ` Andrii Nakryiko
2025-11-10 2:04 ` Donglin Peng
2025-11-04 13:40 ` [RFC PATCH v4 4/7] libbpf: Implement lazy sorting validation for binary search optimization Donglin Peng
2025-11-05 0:29 ` Eduard Zingerman
2025-11-04 13:40 ` [RFC PATCH v4 5/7] btf: Optimize type lookup with binary search Donglin Peng
2025-11-04 17:14 ` Alexei Starovoitov
2025-11-05 13:22 ` Donglin Peng
2025-11-04 13:40 ` [RFC PATCH v4 6/7] btf: Add lazy sorting validation for " Donglin Peng
2025-11-04 13:40 ` [RFC PATCH v4 7/7] selftests/bpf: Add test cases for btf__permute functionality Donglin Peng
2025-11-05 0:41 ` 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=61e92756ea7f202f2e501747b574e97b2f5bc32f.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=alan.maguire@oracle.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dolinux.peng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pengdonglin@xiaomi.com \
--cc=song@kernel.org \
/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