Messages in this thread | | | Date | Wed, 10 Sep 2014 10:28:25 -0700 | Subject | Re: [PATCH v11 net-next 00/12] eBPF syscall, verifier, testsuite | From | Alexei Starovoitov <> |
| |
On Wed, Sep 10, 2014 at 1:19 AM, Daniel Borkmann <dborkman@redhat.com> wrote: >> >> In the future maps can have different types: hash, array, bloom >> filter, >> radix-tree, but currently only hash type is supported: >> enum bpf_map_type { >> BPF_MAP_TYPE_UNSPEC, >> BPF_MAP_TYPE_HASH, >> }; > > > If we mention them here in the man page, users are going to request > them, naturally. ;) So I'd just mention what we have, not what we do > not yet have. But I'm wondering how much library boiler plate only > for BPF we want to add in future, hopefully not most of what's in > Corman ... ? ;)
:) as cover letter says hash type was moved from this set to later series, so it's implemented. array and radix-tree are implemented as well, but not ready for review yet. I have strong use cases for them. Even two of the simplest examples for tracing (ex2 and ex3) will benefit from 'array' type. For bloomfiler type Chema had a strong use case as well. I was assuming he will implement it sooner or later ;) But, surely, I can drop future features from the manpage.
| |