Re: [PATCH 09/14] resource limits: track highwater mark of locked memory

2016-07-18 Thread Oleg Nesterov
On 07/15, Topi Miettinen wrote: > > On 07/15/16 15:14, Oleg Nesterov wrote: > > > > Btw this is not right. The same for the previous patch which tracks > > RLIMIT_STACK. The "current" task can debugger/etc. > > acct_stack_growth() is called from expand_upwards() and > expand_downwards(). They call

Re: [PATCH 09/14] resource limits: track highwater mark of locked memory

2016-07-15 Thread Topi Miettinen
On 07/15/16 15:14, Oleg Nesterov wrote: > On 07/15, Topi Miettinen wrote: >> >> Track maximum size of locked memory, to be able to configure >> RLIMIT_MEMLOCK resource limits. The information is available >> with taskstats and cgroupstats netlink socket. > > So I personally still dislike the very

Re: [PATCH 09/14] resource limits: track highwater mark of locked memory

2016-07-15 Thread Oleg Nesterov
On 07/15, Topi Miettinen wrote: > > Track maximum size of locked memory, to be able to configure > RLIMIT_MEMLOCK resource limits. The information is available > with taskstats and cgroupstats netlink socket. So I personally still dislike the very idea of this series... but I won't argue if you co

[PATCH 09/14] resource limits: track highwater mark of locked memory

2016-07-15 Thread Topi Miettinen
Track maximum size of locked memory, to be able to configure RLIMIT_MEMLOCK resource limits. The information is available with taskstats and cgroupstats netlink socket. Signed-off-by: Topi Miettinen --- arch/ia64/kernel/perfmon.c | 1 + arch/powerpc/kvm/book3s_64_vio.c