From: Jesper Dangaard Brouer <brouer@redhat.com>
To: David Ahern <dsahern@kernel.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
toke@redhat.com, daniel@iogearbox.net, john.fastabend@gmail.com,
ast@kernel.org, kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
andriin@fb.com, dsahern@gmail.com, brouer@redhat.com,
Lorenzo Bianconi <lorenzo@kernel.org>
Subject: Re: [PATCH RFC bpf-next 1/4] bpf: Handle 8-byte values in DEVMAP and DEVMAP_HASH
Date: Fri, 22 May 2020 14:08:05 +0200 [thread overview]
Message-ID: <20200522140805.045b8823@carbon> (raw)
In-Reply-To: <20200522010526.14649-2-dsahern@kernel.org>
On Thu, 21 May 2020 19:05:23 -0600
David Ahern <dsahern@kernel.org> wrote:
> Add support to DEVMAP and DEVMAP_HASH to support 8-byte values as a
> <device index, program id> pair. To do this, a new struct is needed in
> bpf_dtab_netdev to hold the values to return on lookup.
I would like to see us leverage BTF instead of checking on the size
attr->value_size. E.g do the sanity check based on BTF.
Given I don't know the exact details on how this should be done, I will
look into it... I already promised Lorenzo, as we have already
discussed this on IRC.
So, you can Lorenzo can go ahead with this approach, and test the
use-case. And I'll try to figure out if-and-how we can leverage BTF
here. Input from BTF experts will be much appreciated.
> Signed-off-by: David Ahern <dsahern@kernel.org>
> ---
> kernel/bpf/devmap.c | 53 ++++++++++++++++++++++++++++++++++-----------
> 1 file changed, 40 insertions(+), 13 deletions(-)
>
> diff --git a/kernel/bpf/devmap.c b/kernel/bpf/devmap.c
> index a51d9fb7a359..2c01ce434306 100644
> --- a/kernel/bpf/devmap.c
> +++ b/kernel/bpf/devmap.c
> @@ -60,12 +60,19 @@ struct xdp_dev_bulk_queue {
> unsigned int count;
> };
>
> +/* devmap value can be dev index or dev index + prog id */
> +struct dev_map_ext_val {
> + u32 ifindex; /* must be first for compat with 4-byte values */
> + u32 prog_id;
> +};
> +
> struct bpf_dtab_netdev {
> struct net_device *dev; /* must be first member, due to tracepoint */
> struct hlist_node index_hlist;
> struct bpf_dtab *dtab;
> struct rcu_head rcu;
> unsigned int idx;
> + struct dev_map_ext_val val;
> };
>
> struct bpf_dtab {
> @@ -108,9 +115,13 @@ static int dev_map_init_map(struct bpf_dtab *dtab, union bpf_attr *attr)
> u64 cost = 0;
> int err;
>
> - /* check sanity of attributes */
> + /* check sanity of attributes. 2 value sizes supported:
> + * 4 bytes: ifindex
> + * 8 bytes: ifindex + prog id
> + */
> if (attr->max_entries == 0 || attr->key_size != 4 ||
> - attr->value_size != 4 || attr->map_flags & ~DEV_CREATE_FLAG_MASK)
> + (attr->value_size != 4 && attr->value_size != 8) ||
> + attr->map_flags & ~DEV_CREATE_FLAG_MASK)
> return -EINVAL;
>
> /* Lookup returns a pointer straight to dev->ifindex, so make sure the
[...]
> static int __dev_map_update_elem(struct net *net, struct bpf_map *map,
> @@ -568,8 +579,16 @@ static int __dev_map_update_elem(struct net *net, struct bpf_map *map,
> {
> struct bpf_dtab *dtab = container_of(map, struct bpf_dtab, map);
> struct bpf_dtab_netdev *dev, *old_dev;
> - u32 ifindex = *(u32 *)value;
> u32 i = *(u32 *)key;
> + u32 ifindex;
> +
> + if (map->value_size == 4) {
> + ifindex = *(u32 *)value;
> + } else {
> + struct dev_map_ext_val *val = value;
> +
> + ifindex = val->ifindex;
> + }
>
> if (unlikely(map_flags > BPF_EXIST))
> return -EINVAL;
> @@ -609,10 +628,18 @@ static int __dev_map_hash_update_elem(struct net *net, struct bpf_map *map,
> {
> struct bpf_dtab *dtab = container_of(map, struct bpf_dtab, map);
> struct bpf_dtab_netdev *dev, *old_dev;
> - u32 ifindex = *(u32 *)value;
> u32 idx = *(u32 *)key;
> unsigned long flags;
> int err = -EEXIST;
> + u32 ifindex;
> +
> + if (map->value_size == 4) {
> + ifindex = *(u32 *)value;
> + } else {
> + struct dev_map_ext_val *val = value;
> +
> + ifindex = val->ifindex;
> + }
>
> if (unlikely(map_flags > BPF_EXIST || !ifindex))
> return -EINVAL;
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2020-05-22 12:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 1:05 [PATCH RFC bpf-next 0/4] bpf: Add support for XDP programs in DEVMAPs David Ahern
2020-05-22 1:05 ` [PATCH RFC bpf-next 1/4] bpf: Handle 8-byte values in DEVMAP and DEVMAP_HASH David Ahern
2020-05-22 12:08 ` Jesper Dangaard Brouer [this message]
2020-05-22 16:04 ` Jesper Dangaard Brouer
2020-05-22 18:11 ` David Ahern
2020-05-22 1:05 ` [PATCH RFC bpf-next 2/4] bpf: Add support to attach bpf program to a devmap David Ahern
2020-05-22 16:02 ` Toke Høiland-Jørgensen
2020-05-22 17:45 ` David Ahern
2020-05-22 1:05 ` [PATCH RFC bpf-next 3/4] xdp: Add xdp_txq_info to xdp_buff David Ahern
2020-05-22 16:04 ` Toke Høiland-Jørgensen
2020-05-22 17:45 ` David Ahern
2020-05-22 1:05 ` [PATCH RFC bpf-next 4/4] bpftool: Add SEC name for xdp programs attached to device map David Ahern
2020-05-22 11:17 ` [PATCH RFC bpf-next 0/4] bpf: Add support for XDP programs in DEVMAPs Jesper Dangaard Brouer
2020-05-22 15:59 ` Toke Høiland-Jørgensen
2020-05-22 17:46 ` David Ahern
2020-05-25 12:15 ` Toke Høiland-Jørgensen
2020-05-25 12:47 ` Jesper Dangaard Brouer
2020-05-25 12:56 ` Toke Høiland-Jørgensen
2020-05-26 23:36 ` Daniel Borkmann
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=20200522140805.045b8823@carbon \
--to=brouer@redhat.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=dsahern@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kuba@kernel.org \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=toke@redhat.com \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).