Re: [PATCH bpf-next v3 00/29] bpf: switch to memcg-based memory accounting

2020-08-03 Thread Roman Gushchin
On Mon, Aug 03, 2020 at 08:37:15PM +0200, Daniel Borkmann wrote: > On 8/3/20 7:05 PM, Roman Gushchin wrote: > > On Mon, Aug 03, 2020 at 06:39:01PM +0200, Daniel Borkmann wrote: > > > On 8/3/20 5:34 PM, Roman Gushchin wrote: > > > > On Mon, Aug 03, 2020 at 02:05:29PM +0200, Daniel Borkmann wrote: >

Re: [PATCH bpf-next v3 00/29] bpf: switch to memcg-based memory accounting

2020-08-03 Thread Daniel Borkmann
On 8/3/20 7:05 PM, Roman Gushchin wrote: On Mon, Aug 03, 2020 at 06:39:01PM +0200, Daniel Borkmann wrote: On 8/3/20 5:34 PM, Roman Gushchin wrote: On Mon, Aug 03, 2020 at 02:05:29PM +0200, Daniel Borkmann wrote: On 7/30/20 11:22 PM, Roman Gushchin wrote: Currently bpf is using the memlock

Re: [PATCH bpf-next v3 00/29] bpf: switch to memcg-based memory accounting

2020-08-03 Thread Roman Gushchin
On Mon, Aug 03, 2020 at 06:39:01PM +0200, Daniel Borkmann wrote: > On 8/3/20 5:34 PM, Roman Gushchin wrote: > > On Mon, Aug 03, 2020 at 02:05:29PM +0200, Daniel Borkmann wrote: > > > On 7/30/20 11:22 PM, Roman Gushchin wrote: > > > > Currently bpf is using the memlock rlimit for the memory

Re: [PATCH bpf-next v3 00/29] bpf: switch to memcg-based memory accounting

2020-08-03 Thread Daniel Borkmann
On 8/3/20 5:34 PM, Roman Gushchin wrote: On Mon, Aug 03, 2020 at 02:05:29PM +0200, Daniel Borkmann wrote: On 7/30/20 11:22 PM, Roman Gushchin wrote: Currently bpf is using the memlock rlimit for the memory accounting. This approach has its downsides and over time has created a significant

Re: [PATCH bpf-next v3 00/29] bpf: switch to memcg-based memory accounting

2020-08-03 Thread Roman Gushchin
On Mon, Aug 03, 2020 at 02:05:29PM +0200, Daniel Borkmann wrote: > On 7/30/20 11:22 PM, Roman Gushchin wrote: > > Currently bpf is using the memlock rlimit for the memory accounting. > > This approach has its downsides and over time has created a significant > > amount of problems: > > > > 1) The

Re: [PATCH bpf-next v3 00/29] bpf: switch to memcg-based memory accounting

2020-08-03 Thread Daniel Borkmann
On 7/30/20 11:22 PM, Roman Gushchin wrote: Currently bpf is using the memlock rlimit for the memory accounting. This approach has its downsides and over time has created a significant amount of problems: 1) The limit is per-user, but because most bpf operations are performed as root, the

[PATCH bpf-next v3 00/29] bpf: switch to memcg-based memory accounting

2020-07-30 Thread Roman Gushchin
Currently bpf is using the memlock rlimit for the memory accounting. This approach has its downsides and over time has created a significant amount of problems: 1) The limit is per-user, but because most bpf operations are performed as root, the limit has a little value. 2) It's hard to come