netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Andrii Nakryiko <andriin@fb.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@fb.com,
	daniel@iogearbox.net, toke@redhat.com, andrii.nakryiko@gmail.com,
	kernel-team@fb.com
Subject: Re: [PATCH v3 bpf-next 0/3] Add BTF-defined map-in-map support to libbpf
Date: Tue, 28 Apr 2020 17:37:15 -0700	[thread overview]
Message-ID: <20200429003715.p4xydibqfneam4uf@ast-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20200429002739.48006-1-andriin@fb.com>

On Tue, Apr 28, 2020 at 05:27:36PM -0700, Andrii Nakryiko wrote:
> This patch set teaches libbpf how to declare and initialize ARRAY_OF_MAPS and
> HASH_OF_MAPS maps. See patch #3 for all the details.
> 
> Patch #1 refactors parsing BTF definition of map to re-use it cleanly for
> inner map definition parsing.
> 
> Patch #2 refactors map creation and destruction logic for reuse. It also fixes
> existing bug with not closing successfully created maps when bpf_object map
> creation overall fails.
> 
> Patch #3 adds support for an extension of BTF-defined map syntax, as well as
> parsing, recording, and use of relocations to allow declaratively initialize
> outer maps with references to inner maps.
> 
> v1->v2:
>   - rename __inner to __array (Alexei).

Applied, Thanks

      parent reply	other threads:[~2020-04-29  0:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29  0:27 [PATCH v3 bpf-next 0/3] Add BTF-defined map-in-map support to libbpf Andrii Nakryiko
2020-04-29  0:27 ` [PATCH v3 bpf-next 1/3] libbpf: refactor BTF-defined map definition parsing logic Andrii Nakryiko
2020-04-29  0:27 ` [PATCH v3 bpf-next 2/3] libbpf: refactor map creation logic and fix cleanup leak Andrii Nakryiko
2020-04-29  0:27 ` [PATCH v3 bpf-next 3/3] libbpf: add BTF-defined map-in-map support Andrii Nakryiko
2020-04-29  0:37 ` Alexei Starovoitov [this message]

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=20200429003715.p4xydibqfneam4uf@ast-mbp.dhcp.thefacebook.com \
    --to=alexei.starovoitov@gmail.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andriin@fb.com \
    --cc=ast@fb.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=toke@redhat.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).