From: Mauricio Vasquez B <mauricio.vasquez@polito.it>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
netdev@vger.kernel.org
Cc: Song Liu <liu.song.a23@gmail.com>
Subject: [PATCH bpf-next v2 1/7] bpf: rename stack trace map operations
Date: Wed, 10 Oct 2018 16:05:58 +0200 [thread overview]
Message-ID: <153918035870.8915.8092114744007418400.stgit@kernel> (raw)
In-Reply-To: <153918035266.8915.12458090320382567494.stgit@kernel>
In the following patches queue and stack maps (FIFO and LIFO
datastructures) will be implemented. In order to avoid confusion and
a possible name clash rename stack_map_ops to stack_trace_map_ops
Signed-off-by: Mauricio Vasquez B <mauricio.vasquez@polito.it>
---
include/linux/bpf_types.h | 2 +-
kernel/bpf/stackmap.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/bpf_types.h b/include/linux/bpf_types.h
index 5432f4c9f50e..658509daacd4 100644
--- a/include/linux/bpf_types.h
+++ b/include/linux/bpf_types.h
@@ -51,7 +51,7 @@ BPF_MAP_TYPE(BPF_MAP_TYPE_LRU_HASH, htab_lru_map_ops)
BPF_MAP_TYPE(BPF_MAP_TYPE_LRU_PERCPU_HASH, htab_lru_percpu_map_ops)
BPF_MAP_TYPE(BPF_MAP_TYPE_LPM_TRIE, trie_map_ops)
#ifdef CONFIG_PERF_EVENTS
-BPF_MAP_TYPE(BPF_MAP_TYPE_STACK_TRACE, stack_map_ops)
+BPF_MAP_TYPE(BPF_MAP_TYPE_STACK_TRACE, stack_trace_map_ops)
#endif
BPF_MAP_TYPE(BPF_MAP_TYPE_ARRAY_OF_MAPS, array_of_maps_map_ops)
BPF_MAP_TYPE(BPF_MAP_TYPE_HASH_OF_MAPS, htab_of_maps_map_ops)
diff --git a/kernel/bpf/stackmap.c b/kernel/bpf/stackmap.c
index b2ade10f7ec3..90daf285de03 100644
--- a/kernel/bpf/stackmap.c
+++ b/kernel/bpf/stackmap.c
@@ -600,7 +600,7 @@ static void stack_map_free(struct bpf_map *map)
put_callchain_buffers();
}
-const struct bpf_map_ops stack_map_ops = {
+const struct bpf_map_ops stack_trace_map_ops = {
.map_alloc = stack_map_alloc,
.map_free = stack_map_free,
.map_get_next_key = stack_map_get_next_key,
next prev parent reply other threads:[~2018-10-10 21:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 14:05 [PATCH bpf-next v2 0/7] Implement queue/stack maps Mauricio Vasquez B
2018-10-10 14:05 ` Mauricio Vasquez B [this message]
2018-10-10 16:15 ` [PATCH bpf-next v2 1/7] bpf: rename stack trace map operations Song Liu
2018-10-10 14:06 ` [PATCH bpf-next v2 2/7] bpf/syscall: allow key to be null in map functions Mauricio Vasquez B
2018-10-10 16:09 ` Song Liu
2018-10-10 14:06 ` [PATCH bpf-next v2 3/7] bpf: add MAP_LOOKUP_AND_DELETE_ELEM syscall Mauricio Vasquez B
2018-10-10 16:48 ` Song Liu
2018-10-10 17:47 ` Mauricio Vasquez
2018-10-10 22:34 ` Song Liu
2018-10-10 22:50 ` Mauricio Vasquez
2018-10-11 23:51 ` Alexei Starovoitov
2018-10-16 21:16 ` Mauricio Vasquez
2018-10-16 23:20 ` Alexei Starovoitov
2018-10-17 2:29 ` Mauricio Vasquez
2018-10-10 14:06 ` [PATCH bpf-next v2 4/7] bpf/verifier: add ARG_PTR_TO_UNINIT_MAP_VALUE Mauricio Vasquez B
2018-10-10 16:10 ` Song Liu
2018-10-10 14:06 ` [PATCH bpf-next v2 5/7] bpf: add queue and stack maps Mauricio Vasquez B
2018-10-10 14:06 ` [PATCH bpf-next v2 6/7] Sync uapi/bpf.h to tools/include Mauricio Vasquez B
2018-10-10 16:14 ` Song Liu
2018-10-10 14:06 ` [PATCH bpf-next v2 7/7] selftests/bpf: add test cases for queue and stack maps Mauricio Vasquez B
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=153918035870.8915.8092114744007418400.stgit@kernel \
--to=mauricio.vasquez@polito.it \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=liu.song.a23@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).