From: Kui-Feng Lee <sinquersw@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Kui-Feng Lee <thinker.li@gmail.com>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, Kernel Team <kernel-team@meta.com>,
Andrii Nakryiko <andrii@kernel.org>,
Kui-Feng Lee <kuifeng@meta.com>
Subject: Re: [RFC bpf-next] Registering struct_ops types from modules.
Date: Fri, 8 Sep 2023 14:03:17 -0700 [thread overview]
Message-ID: <b1c35333-013b-2f3a-e6cd-c00530e8a6cf@gmail.com> (raw)
In-Reply-To: <CAADnVQLAmvNewqyVUZkcFt8RRvs+W0RJfyExa-gZ=-0-nwL16A@mail.gmail.com>
On 9/8/23 11:24, Alexei Starovoitov wrote:
> On Thu, Sep 7, 2023 at 1:32 PM <thinker.li@gmail.com> wrote:
>>
>> From: Kui-Feng Lee <thinker.li@gmail.com>
>>
>> Resend to remove noise!
>>
>> Given the current constraints of the current implementation, struct_ops
>> cannot be registered dynamically. This presents a significant limitation
>> for modules like fuse-bpf, which seeks to implement a new struct_ops
>> type. To address this issue, here it proposes the introduction of a new
>> API. This API will enable the registering of new struct_ops types from
>> modules.
>>
>> The following code is an example of how to implement a new struct_ops type
>> in a module with the proposed API. It adds a new type bpf_testmod_ops in
>> the bpf_testmod module. And, call register_bpf_struct_ops() and
>> unregister_bpf_struct_ops() when init and exit the module.
>
> register_bpf_struct_ops() api implementation is missing in the diff.
Sorry for the confusion!
The purpose of this RFC to check how people think about the API itself.
next prev parent reply other threads:[~2023-09-08 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 20:32 [RFC bpf-next] Registering struct_ops types from modules thinker.li
2023-09-08 18:24 ` Alexei Starovoitov
2023-09-08 21:03 ` Kui-Feng Lee [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-07 20:26 thinker.li
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=b1c35333-013b-2f3a-e6cd-c00530e8a6cf@gmail.com \
--to=sinquersw@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=kernel-team@meta.com \
--cc=kuifeng@meta.com \
--cc=martin.lau@linux.dev \
--cc=song@kernel.org \
--cc=thinker.li@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox