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
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.
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
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.
>>
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
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
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
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
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
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
10 matches
Mail list logo