From: Eduard Zingerman <eddyz87@gmail.com>
To: Donglin Peng <dolinux.peng@gmail.com>, ast@kernel.org
Cc: linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Alan Maguire <alan.maguire@oracle.com>,
Song Liu <song@kernel.org>, pengdonglin <pengdonglin@xiaomi.com>
Subject: Re: [RFC PATCH v4 2/7] libbpf: Add BTF permutation support for type reordering
Date: Tue, 04 Nov 2025 15:45:04 -0800 [thread overview]
Message-ID: <f16e34ac93438c9ccb9b174d45060c3b06b45e9d.camel@gmail.com> (raw)
In-Reply-To: <20251104134033.344807-3-dolinux.peng@gmail.com>
On Tue, 2025-11-04 at 21:40 +0800, Donglin Peng wrote:
> From: pengdonglin <pengdonglin@xiaomi.com>
>
> Introduce btf__permute() API to allow in-place rearrangement of BTF types.
> This function reorganizes BTF type order according to a provided array of
> type IDs, updating all type references to maintain consistency.
>
> The permutation process involves:
> 1. Shuffling types into new order based on the provided ID mapping
> 2. Remapping all type ID references to point to new locations
> 3. Handling BTF extension data if provided via options
>
> This is particularly useful for optimizing type locality after BTF
> deduplication or for meeting specific layout requirements in specialized
> use cases.
>
> Cc: Eduard Zingerman <eddyz87@gmail.com>
> Cc: Alexei Starovoitov <ast@kernel.org>
> Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>
> Cc: Alan Maguire <alan.maguire@oracle.com>
> Cc: Song Liu <song@kernel.org>
> Signed-off-by: pengdonglin <pengdonglin@xiaomi.com>
> Signed-off-by: Donglin Peng <dolinux.peng@gmail.com>
Acked-by: Eduard Zingerman <eddyz87@gmail.com>
[...]
> --- a/tools/lib/bpf/btf.h
> +++ b/tools/lib/bpf/btf.h
> @@ -273,6 +273,40 @@ LIBBPF_API int btf__dedup(struct btf *btf, const struct btf_dedup_opts *opts);
> */
> LIBBPF_API int btf__relocate(struct btf *btf, const struct btf *base_btf);
>
> +struct btf_permute_opts {
> + size_t sz;
> + /* optional .BTF.ext info along the main BTF info */
> + struct btf_ext *btf_ext;
> + size_t :0;
> +};
> +#define btf_permute_opts__last_field btf_ext
> +
> +/**
> + * @brief **btf__permute()** rearranges BTF types in-place according to specified mapping
> + * @param btf BTF object to permute
> + * @param ids Array defining new type order. Must contain exactly btf->nr_types elements,
> + * each being a valid type ID in range [btf->start_id, btf->start_id + btf->nr_types - 1]
> + * @param opts Optional parameters, including BTF extension data for reference updates
> + * @return 0 on success, negative error code on failure
> + *
> + * **btf__permute()** performs an in-place permutation of BTF types, rearranging them
> + * according to the order specified in @p ids array. After reordering, all type references
> + * within the BTF data and optional BTF extension are updated to maintain consistency.
> + *
> + * The permutation process consists of two phases:
> + * 1. Type shuffling: Physical reordering of type data in memory
> + * 2. Reference remapping: Updating all type ID references to new locations
Nit: Please drop this paragraph: it is an implementation detail, not
user-facing behavior, and it is obvious from the function code.
> + *
> + * This is particularly useful for optimizing type locality after BTF deduplication
> + * or for meeting specific layout requirements in specialized use cases.
Nit: Please drop this paragraph as well.
> + *
> + * On error, negative error code is returned and errno is set appropriately.
> + * Common error codes include:
> + * - -EINVAL: Invalid parameters or invalid ID mapping (e.g., duplicate IDs, out-of-range IDs)
> + * - -ENOMEM: Memory allocation failure during permutation process
> + */
> +LIBBPF_API int btf__permute(struct btf *btf, __u32 *ids, const struct btf_permute_opts *opts);
> +
> struct btf_dump;
>
> struct btf_dump_opts {
[...]
next prev parent reply other threads:[~2025-11-04 23:45 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
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 [this message]
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=f16e34ac93438c9ccb9b174d45060c3b06b45e9d.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