Re: [RFC 05/18] limits: track and present RLIMIT_NOFILE actual max

2016-06-14 Thread Topi Miettinen
On 06/13/16 21:16, Andy Lutomirski wrote: > On Mon, Jun 13, 2016 at 2:13 PM, Topi Miettinen wrote: >> On 06/13/16 20:40, Andy Lutomirski wrote: >>> On 06/13/2016 12:44 PM, Topi Miettinen wrote: Track maximum number of files for the process, present current maximum in

Re: [RFC 05/18] limits: track and present RLIMIT_NOFILE actual max

2016-06-14 Thread Topi Miettinen
On 06/13/16 21:16, Andy Lutomirski wrote: > On Mon, Jun 13, 2016 at 2:13 PM, Topi Miettinen wrote: >> On 06/13/16 20:40, Andy Lutomirski wrote: >>> On 06/13/2016 12:44 PM, Topi Miettinen wrote: Track maximum number of files for the process, present current maximum in /proc/self/limits.

Re: [RFC 05/18] limits: track and present RLIMIT_NOFILE actual max

2016-06-13 Thread Andy Lutomirski
On Mon, Jun 13, 2016 at 2:13 PM, Topi Miettinen wrote: > On 06/13/16 20:40, Andy Lutomirski wrote: >> On 06/13/2016 12:44 PM, Topi Miettinen wrote: >>> Track maximum number of files for the process, present current maximum >>> in /proc/self/limits. >> >> The core part should

Re: [RFC 05/18] limits: track and present RLIMIT_NOFILE actual max

2016-06-13 Thread Andy Lutomirski
On Mon, Jun 13, 2016 at 2:13 PM, Topi Miettinen wrote: > On 06/13/16 20:40, Andy Lutomirski wrote: >> On 06/13/2016 12:44 PM, Topi Miettinen wrote: >>> Track maximum number of files for the process, present current maximum >>> in /proc/self/limits. >> >> The core part should be its own patch. >>

Re: [RFC 05/18] limits: track and present RLIMIT_NOFILE actual max

2016-06-13 Thread Topi Miettinen
On 06/13/16 20:40, Andy Lutomirski wrote: > On 06/13/2016 12:44 PM, Topi Miettinen wrote: >> Track maximum number of files for the process, present current maximum >> in /proc/self/limits. > > The core part should be its own patch. > > Also, you have this weirdly named (and racy!) function

Re: [RFC 05/18] limits: track and present RLIMIT_NOFILE actual max

2016-06-13 Thread Topi Miettinen
On 06/13/16 20:40, Andy Lutomirski wrote: > On 06/13/2016 12:44 PM, Topi Miettinen wrote: >> Track maximum number of files for the process, present current maximum >> in /proc/self/limits. > > The core part should be its own patch. > > Also, you have this weirdly named (and racy!) function

Re: [RFC 05/18] limits: track and present RLIMIT_NOFILE actual max

2016-06-13 Thread Andy Lutomirski
On 06/13/2016 12:44 PM, Topi Miettinen wrote: Track maximum number of files for the process, present current maximum in /proc/self/limits. The core part should be its own patch. Also, you have this weirdly named (and racy!) function bump_rlimit. Wouldn't this be nicer if you taught the

Re: [RFC 05/18] limits: track and present RLIMIT_NOFILE actual max

2016-06-13 Thread Andy Lutomirski
On 06/13/2016 12:44 PM, Topi Miettinen wrote: Track maximum number of files for the process, present current maximum in /proc/self/limits. The core part should be its own patch. Also, you have this weirdly named (and racy!) function bump_rlimit. Wouldn't this be nicer if you taught the

[RFC 05/18] limits: track and present RLIMIT_NOFILE actual max

2016-06-13 Thread Topi Miettinen
Track maximum number of files for the process, present current maximum in /proc/self/limits. Signed-off-by: Topi Miettinen --- fs/file.c | 4 fs/proc/base.c| 10 ++ include/linux/sched.h | 7 +++ 3 files changed, 17 insertions(+), 4

[RFC 05/18] limits: track and present RLIMIT_NOFILE actual max

2016-06-13 Thread Topi Miettinen
Track maximum number of files for the process, present current maximum in /proc/self/limits. Signed-off-by: Topi Miettinen --- fs/file.c | 4 fs/proc/base.c| 10 ++ include/linux/sched.h | 7 +++ 3 files changed, 17 insertions(+), 4 deletions(-) diff