Re: [PATCH v2 bpf 1/2] bpf: skip non exist keys in generic_map_lookup_batch

On Thu, Feb 6, 2025 at 9:45 PM Yan Zhai wrote: > > The generic_map_lookup_batch currently returns EINTR if it fails with > ENOENT and retries several times on bpf_map_copy_value. The next batch > would start from the same location, presuming it's a transient issue. > This is incorrect if a map can

Re: [PATCH v2 bpf 1/2] bpf: skip non exist keys in generic_map_lookup_batch

On 2/7/2025 1:45 PM, Yan Zhai wrote: > The generic_map_lookup_batch currently returns EINTR if it fails with > ENOENT and retries several times on bpf_map_copy_value. The next batch > would start from the same location, presuming it's a transient issue. > This is incorrect if a map can actually

[PATCH v2 bpf 1/2] bpf: skip non exist keys in generic_map_lookup_batch

The generic_map_lookup_batch currently returns EINTR if it fails with ENOENT and retries several times on bpf_map_copy_value. The next batch would start from the same location, presuming it's a transient issue. This is incorrect if a map can actually have "holes", i.e. "get_next_key" can return a k