From: Joel Fernandes <joelaf@google.com>
To: linux-kernel@vger.kernel.org
Cc: iovisor-dev@lists.iovisor.org, kernel-team@android.com,
Joel Fernandes <joelaf@google.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Brendan Gregg <bgregg@netflix.com>,
Brenden Blanco <bblanco@gmail.com>
Subject: [PATCH] bpf/stackmap: Implement bpf_get_next_key
Date: Wed, 24 Jan 2018 20:37:52 -0800 [thread overview]
Message-ID: <20180125043752.35179-1-joelaf@google.com> (raw)
Currently stackmaps can't be iterated over. The keys are obtained
through other maps and look ups have to be performed. In new usecases,
its useful to be able to iterate over the stackmap independently.
Implement bpf_get_next_key to make this possible.
More details of use case:
Currently iterating over stack maps is done like so, for example
in BCC tools offcputime script:
1. Obtain keys from the 'counts' hash map.
2. Look up stackmap with each of the keys obtained from step 1.
This makes the iteration of stackmap dependent on the counts map.
In a new tool I'm working on called BPFd [1], it gives a huge speed
up when I dump entire maps before transmitting them to BCC tools
on a different machine [2]. This patch makes it possible to dump
stackmaps independent of other maps.
Tested on x86 and arm64 machines.
[1] https://lwn.net/Articles/744522/
[2] https://github.com/joelagnel/bpfd/issues/8
Cc: Alexei Starovoitov <ast@kernel.org>
Cc: Daniel Borkmann <daniel@iogearbox.net>
Cc: Brendan Gregg <bgregg@netflix.com>
Cc: Brenden Blanco <bblanco@gmail.com>
Signed-off-by: Joel Fernandes <joelaf@google.com>
---
kernel/bpf/stackmap.c | 18 +++++++++++++++++-
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/kernel/bpf/stackmap.c b/kernel/bpf/stackmap.c
index a15bc636cc98..b0bf7d009f76 100644
--- a/kernel/bpf/stackmap.c
+++ b/kernel/bpf/stackmap.c
@@ -228,7 +228,23 @@ int bpf_stackmap_copy(struct bpf_map *map, void *key, void *value)
static int stack_map_get_next_key(struct bpf_map *map, void *key, void *next_key)
{
- return -EINVAL;
+ struct bpf_stack_map *smap = container_of(map, struct bpf_stack_map, map);
+ u32 id = 0;
+
+ if (key) {
+ id = *(u32 *)key;
+ if (unlikely(id >= smap->n_buckets))
+ return -ENOENT;
+ id++;
+ }
+
+ for ( ; id < smap->n_buckets; id++) {
+ if (READ_ONCE(smap->buckets[id])) {
+ *(u32 *)next_key = id;
+ return 0;
+ }
+ }
+ return -ENOENT;
}
static int stack_map_update_elem(struct bpf_map *map, void *key, void *value,
--
2.16.0.rc1.238.g530d649a79-goog
next reply other threads:[~2018-01-25 4:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 4:37 Joel Fernandes [this message]
2018-01-25 4:42 ` Alexei Starovoitov
2018-01-25 4:53 ` Joel Fernandes
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=20180125043752.35179-1-joelaf@google.com \
--to=joelaf@google.com \
--cc=ast@kernel.org \
--cc=bblanco@gmail.com \
--cc=bgregg@netflix.com \
--cc=daniel@iogearbox.net \
--cc=iovisor-dev@lists.iovisor.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®