Joanne Koong <joannekoong@xxxxxx> writes:
> This patch adds the kernel-side changes for the implementation of
> a bitset map with bloom filter capabilities.
>
> The bitset map does not have keys, only values since it is a
> non-associative data type. When the bitset map is created, it must
> be created with a key_size of 0, and the max_entries value should be the
> desired size of the bitset, in number of bits.
>
> The bitset map supports peek (determining whether a bit is set in the
> map), push (setting a bit in the map), and pop (clearing a bit in the
> map) operations. These operations are exposed to userspace applications
> through the already existing syscalls in the following way:
>
> BPF_MAP_UPDATE_ELEM -> bpf_map_push_elem
> BPF_MAP_LOOKUP_ELEM -> bpf_map_peek_elem
> BPF_MAP_LOOKUP_AND_DELETE_ELEM -> bpf_map_pop_elem
>
> For updates, the user will pass in a NULL key and the index of the
> bit to set in the bitmap as the value. For lookups, the user will pass
> in the index of the bit to check as the value. If the bit is set, 0
> will be returned, else -ENOENT. For clearing the bit, the user will pass
> in the index of the bit to clear as the value.
This is interesting, and I can see other uses of such a data structure.
However, a couple of questions (talking mostly about the 'raw' bitmap
without the bloom filter enabled):
- How are you envisioning synchronisation to work? The code is using the
atomic set_bit() operation, but there's no test_and_{set,clear}_bit().
Any thoughts on how users would do this?
- It would be useful to expose the "find first set (ffs)" operation of
the bitmap as well. This can be added later, but thinking about the
API from the start would be good to avoid having to add a whole
separate helper for this. My immediate thought is to reserve peek(-1)
for this use - WDYT?
- Any thoughts on inlining the lookups? This should at least be feasible
for the non-bloom-filter type, but I'm not quite sure if the use of
map_extra allows the verifier to distinguish between the map types
(I'm a little fuzzy on how the inlining actually works)? And can
peek()/push()/pop() be inlined at all?
-Toke
