lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 8 Nov 2019 15:19:59 -0800
From:   Andrii Nakryiko <andrii.nakryiko@...il.com>
To:     Stanislav Fomichev <sdf@...ichev.me>
Cc:     Andrii Nakryiko <andriin@...com>, bpf <bpf@...r.kernel.org>,
        Networking <netdev@...r.kernel.org>,
        Alexei Starovoitov <ast@...com>,
        Daniel Borkmann <daniel@...earbox.net>,
        Kernel Team <kernel-team@...com>
Subject: Re: [PATCH bpf-next 0/3] Add support for memory-mapping BPF array maps

On Fri, Nov 8, 2019 at 2:08 PM Stanislav Fomichev <sdf@...ichev.me> wrote:
>
> On 11/07, Andrii Nakryiko wrote:
> > This patch set adds ability to memory-map BPF array maps (single- and
> > multi-element). The primary use case is memory-mapping BPF array maps, created
> > to back global data variables, created by libbpf implicitly. This allows for
> > much better usability, along with avoiding syscalls to read or update data
> > completely.
> Just wondering: is it something that you plan to extend to other map types?

My main motivation is global data, so normal arrays are the most
important for me. If anyone has any performance-driven use cases, we
can extend others as well, if possible. Not all maps can be easily
mmap()'ed just due to nature of their data. E.g., it's hard to imagine
how hashmap can be mapped. But doing per-cpu arrays should be doable
with good kernel-userspace memory layout "contract".

Powered by blists - more mailing lists