All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Quentin Monnet <quentin@isovalent.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>, bpf <bpf@vger.kernel.org>,
	Network Development <netdev@vger.kernel.org>,
	Andrii Nakryiko <andrii.nakryiko@gmail.com>
Subject: Re: [PATCH bpf-next v3 0/2] tools: bpftool: support creating outer maps
Date: Thu, 10 Sep 2020 17:30:47 -0700	[thread overview]
Message-ID: <CAADnVQL=7+owiok=-uH3HYjMiLGbq0bWnH_E2eBr8CrsQiLuUg@mail.gmail.com> (raw)
In-Reply-To: <20200910102652.10509-1-quentin@isovalent.com>

On Thu, Sep 10, 2020 at 3:27 AM Quentin Monnet <quentin@isovalent.com> wrote:
>
> This series makes bpftool able to create outer maps (maps of types
> array-of-maps and hash-of-maps). This is done by passing the relevant
> inner_map_fd, which we do through a new command-line keyword.
>
> The first two patches also clean up the function related to dumping map
> elements.
>
> v3:
> - Add a check on errno being ENOENT before skipping outer map entry in
>   dumps.

Applied. Thanks

      parent reply	other threads:[~2020-09-11  0:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10 10:26 [PATCH bpf-next v3 0/2] tools: bpftool: support creating outer maps Quentin Monnet
2020-09-10 10:26 ` [PATCH bpf-next v3 1/3] tools: bpftool: clean up function to dump map entry Quentin Monnet
2020-09-10 16:41   ` Andrii Nakryiko
2020-09-10 16:43     ` Andrii Nakryiko
2020-09-10 10:26 ` [PATCH bpf-next v3 2/3] tools: bpftool: keep errors for map-of-map dumps if distinct from ENOENT Quentin Monnet
2020-09-10 16:42   ` Andrii Nakryiko
2020-09-10 16:45     ` Quentin Monnet
2020-09-10 10:26 ` [PATCH bpf-next v3 3/3] tools: bpftool: add "inner_map" to "bpftool map create" outer maps Quentin Monnet
2020-09-11  0:30 ` 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='CAADnVQL=7+owiok=-uH3HYjMiLGbq0bWnH_E2eBr8CrsQiLuUg@mail.gmail.com' \
    --to=alexei.starovoitov@gmail.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=netdev@vger.kernel.org \
    --cc=quentin@isovalent.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 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.