From: "Nikita V. Shirokov" <tehnerd@tehnerd.com>
To: Y Song <ys114321@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jakub Kicinski <jakub.kicinski@netronome.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH bpf-next 1/2] bpf: adding support for map in map in libbpf
Date: Mon, 19 Nov 2018 17:38:05 -0800 [thread overview]
Message-ID: <20181120013805.GB1588@maindev> (raw)
In-Reply-To: <CAH3MdRVAWsk9RY4qO3sCyFhVM8FYR+em4cNuYcXpuZCtEYv4pA@mail.gmail.com>
On Mon, Nov 19, 2018 at 05:12:43PM -0800, Y Song wrote:
> On Mon, Nov 19, 2018 at 4:13 PM Nikita V. Shirokov <tehnerd@tehnerd.com> wrote:
> >
> > idea is pretty simple. for specified map (pointed by struct bpf_map)
> > we would provide descriptor of already loaded map, which is going to be
> > used as a prototype for inner map. proposed workflow:
> > 1) open bpf's object (bpf_object__open)
> > 2) create bpf's map which is going to be used as a prototype
> > 3) find (by name) map-in-map which you want to load and update w/
> > descriptor of inner map w/ a new helper from this patch
> > 4) load bpf program w/ bpf_object__load
> >
> > inner_map_fd is ignored by any other maps asidef from (hash|array) of
> > maps
> >
> > Signed-off-by: Nikita V. Shirokov <tehnerd@tehnerd.com>
> > ---
> > tools/lib/bpf/libbpf.c | 7 +++++++
> > tools/lib/bpf/libbpf.h | 2 ++
> > 2 files changed, 9 insertions(+)
> >
> > diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
> > index a01eb9584e52..a2ee1b1a93b6 100644
> > --- a/tools/lib/bpf/libbpf.c
> > +++ b/tools/lib/bpf/libbpf.c
> > @@ -163,6 +163,7 @@ struct bpf_map {
> > char *name;
> > size_t offset;
> > int map_ifindex;
> > + int inner_map_fd;
> > struct bpf_map_def def;
> > __u32 btf_key_type_id;
> > __u32 btf_value_type_id;
> > @@ -1146,6 +1147,7 @@ bpf_object__create_maps(struct bpf_object *obj)
> > create_attr.btf_fd = 0;
> > create_attr.btf_key_type_id = 0;
> > create_attr.btf_value_type_id = 0;
> > + create_attr.inner_map_fd = map->inner_map_fd;
> >
> > if (obj->btf && !bpf_map_find_btf_info(map, obj->btf)) {
> > create_attr.btf_fd = btf__fd(obj->btf);
> > @@ -2562,6 +2564,11 @@ void bpf_map__set_ifindex(struct bpf_map *map, __u32 ifindex)
> > map->map_ifindex = ifindex;
> > }
> >
> > +void bpf_map__add_inner_map_fd(struct bpf_map *map, const int fd)
>
> Do we need "const" attribute here?
>
i can drop it in v2
> > +{
> > + map->inner_map_fd = fd;
> > +}
> > +
> > static struct bpf_map *
> > __bpf_map__iter(struct bpf_map *m, struct bpf_object *obj, int i)
> > {
> > diff --git a/tools/lib/bpf/libbpf.h b/tools/lib/bpf/libbpf.h
> > index b1686a787102..7cb00cd41789 100644
> > --- a/tools/lib/bpf/libbpf.h
> > +++ b/tools/lib/bpf/libbpf.h
> > @@ -293,6 +293,8 @@ LIBBPF_API void bpf_map__set_ifindex(struct bpf_map *map, __u32 ifindex);
> > LIBBPF_API int bpf_map__pin(struct bpf_map *map, const char *path);
> > LIBBPF_API int bpf_map__unpin(struct bpf_map *map, const char *path);
> >
> > +LIBBPF_API void bpf_map__add_inner_map_fd(struct bpf_map *map, const int fd);
> > +
> > LIBBPF_API long libbpf_get_error(const void *ptr);
> >
> > struct bpf_prog_load_attr {
> > --
> > 2.15.1
> >
next prev parent reply other threads:[~2018-11-20 12:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 0:06 [PATCH bpf-next 0/2] bpf: adding support for mapinmap in libbpf Nikita V. Shirokov
2018-11-20 0:06 ` [PATCH bpf-next 1/2] bpf: adding support for map in map " Nikita V. Shirokov
2018-11-20 1:12 ` Y Song
2018-11-20 1:38 ` Nikita V. Shirokov [this message]
2018-11-20 11:29 ` Edward Cree
2018-11-20 0:06 ` [PATCH bpf-next 2/2] bpf: adding tests for mapinmap helpber " Nikita V. Shirokov
2018-11-20 1:18 ` Y Song
2018-11-20 1:37 ` Nikita V. Shirokov
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=20181120013805.GB1588@maindev \
--to=tehnerd@tehnerd.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=ys114321@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;
as well as URLs for NNTP newsgroup(s).