Re: [RFC bpf-next] libbpf: increase rlimit before trying to create BPF maps

2018-11-02 Thread Quentin Monnet
2018-11-02 10:08 UTC+0100 ~ Daniel Borkmann > On 11/01/2018 06:18 PM, Quentin Monnet wrote: >> 2018-10-30 15:23 UTC+ ~ Quentin Monnet >>> The limit for memory locked in the kernel by a process is usually set to >>> 64 bytes by default. This can be an issue when creating large BPF maps. >>> A

Re: [RFC bpf-next] libbpf: increase rlimit before trying to create BPF maps

2018-11-02 Thread Daniel Borkmann
On 11/01/2018 06:18 PM, Quentin Monnet wrote: > 2018-10-30 15:23 UTC+ ~ Quentin Monnet >> The limit for memory locked in the kernel by a process is usually set to >> 64 bytes by default. This can be an issue when creating large BPF maps. >> A workaround is to raise this limit for the current p

Re: [RFC bpf-next] libbpf: increase rlimit before trying to create BPF maps

2018-11-01 Thread Quentin Monnet
2018-10-30 15:23 UTC+ ~ Quentin Monnet > The limit for memory locked in the kernel by a process is usually set to > 64 bytes by default. This can be an issue when creating large BPF maps. > A workaround is to raise this limit for the current process before > trying to create a new BPF map. Cha

[RFC bpf-next] libbpf: increase rlimit before trying to create BPF maps

2018-10-30 Thread Quentin Monnet
The limit for memory locked in the kernel by a process is usually set to 64 bytes by default. This can be an issue when creating large BPF maps. A workaround is to raise this limit for the current process before trying to create a new BPF map. Changing the hard limit requires the CAP_SYS_RESOURCE a