From: Martin KaFai Lau <martin.lau@linux.dev>
To: Amery Hung <ameryhung@gmail.com>
Cc: netdev@vger.kernel.org, alexei.starovoitov@gmail.com,
andrii@kernel.org, daniel@iogearbox.net, tj@kernel.org,
memxor@gmail.com, martin.lau@kernel.org, kernel-team@meta.com,
bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v1 2/3] selftests/bpf: Add multi_st_ops that supports multiple instances
Date: Mon, 4 Aug 2025 16:43:05 -0700 [thread overview]
Message-ID: <573da832-260f-4fc5-8e8c-38f185e09249@linux.dev> (raw)
In-Reply-To: <20250731210950.3927649-3-ameryhung@gmail.com>
On 7/31/25 2:09 PM, Amery Hung wrote:
> +static int multi_st_ops_reg(void *kdata, struct bpf_link *link)
> +{
> + struct bpf_testmod_multi_st_ops *st_ops =
> + (struct bpf_testmod_multi_st_ops *)kdata;
> + struct bpf_map *map;
> + unsigned long flags;
> + int err = 0;
> +
> + map = bpf_struct_ops_get(kdata);
The bpf_struct_ops_get returns a map pointer and also inc_not_zero() the map
which we know it won't fail at this point, so no check is needed.
> +
> + spin_lock_irqsave(&multi_st_ops_lock, flags);
> + if (multi_st_ops_find_nolock(map->id)) {
> + pr_err("multi_st_ops(id:%d) has already been registered\n", map->id);
> + err = -EEXIST;
> + goto unlock;
> + }
> +
> + st_ops->id = map->id;
> + hlist_add_head(&st_ops->node, &multi_st_ops_list);
> +unlock:
> + bpf_struct_ops_put(kdata);
To get an id, it needs a get and an immediate put. No concern on the performance
but just feels not easy to use. e.g. For the subsystem supporting link_update,
it will need to do this get/put twice. One on the old kdata and another on the
new kdata. Take a look at the bpf_struct_ops_map_link_update().
To create a id->struct_ops mapping, the subsystem needs neither the map pointer
nor incrementing the map refcnt. How about create a new helper to only return
the id of the kdata?
Uncompiled code:
u32 bpf_struct_ops_id(const void *kdata)
{
struct bpf_struct_ops_value *kvalue;
struct bpf_struct_ops_map *st_map;
kvalue = container_of(kdata, struct bpf_struct_ops_value, data);
st_map = container_of(kvalue, struct bpf_struct_ops_map, kvalue);
return st_map->map.id;
}
> + spin_unlock_irqrestore(&multi_st_ops_lock, flags);
> +
> + return err;
> +}
> +
> +static void multi_st_ops_unreg(void *kdata, struct bpf_link *link)
> +{
> + struct bpf_testmod_multi_st_ops *st_ops;
> + struct bpf_map *map;
> + unsigned long flags;
> +
> + map = bpf_struct_ops_get(kdata);
> +
> + spin_lock_irqsave(&multi_st_ops_lock, flags);
> + st_ops = multi_st_ops_find_nolock(map->id);
> + if (st_ops)
> + hlist_del(&st_ops->node);
> + spin_unlock_irqrestore(&multi_st_ops_lock, flags);
> +
> + bpf_struct_ops_put(kdata);
> +}
next prev parent reply other threads:[~2025-08-04 23:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 21:09 [PATCH bpf-next v1 0/3] Allow struct_ops to get bpf_map during Amery Hung
2025-07-31 21:09 ` [PATCH bpf-next v1 1/3] bpf: Allow getting bpf_map from struct_ops kdata Amery Hung
2025-08-01 9:31 ` kernel test robot
2025-07-31 21:09 ` [PATCH bpf-next v1 2/3] selftests/bpf: Add multi_st_ops that supports multiple instances Amery Hung
2025-08-04 23:43 ` Martin KaFai Lau [this message]
2025-08-05 15:27 ` Amery Hung
2025-07-31 21:09 ` [PATCH bpf-next v1 3/3] selftests/bpf: Test multi_st_ops and calling kfuncs from different programs Amery Hung
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=573da832-260f-4fc5-8e8c-38f185e09249@linux.dev \
--to=martin.lau@linux.dev \
--cc=alexei.starovoitov@gmail.com \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@meta.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.