On Thu, 16 Aug 2007 08:35:38 EDT, Neil Horman said:
> Hey again-
> Andrew requested that I repost this cleanly, after running the patch
> through checkpatch. As requested here it is with the changelog.
>
> Currently, there exists no method for a process to query the resource
> limits of another process. They can be inferred via some mechanisms but they
> cannot be explicitly determined. Given that this information can be usefull
to
> know during the debugging of an application, I've written this patch which
> exports all of a processes limits via /proc/<pid>/limits.
>
> Tested successfully by myself on x86 on top of 2.6.23-rc2-mm1.
I had only one comment the first time around, and Neil addressed it.
I've also tested on x86_64 23-rc2-mm1, and it works here too. I saw where this
uses units of 'bytes' while the shell 'ulimit' uses 1024-byte units in some
places, but (a) this lists the units and (b) it's consistent with setrlimit().
Testing with values >4G show it's 64-bit clean as well.
One question: Is the units milliseconds, or seconds here:
+ [RLIMIT_CPU] = {"Max cpu time", "ms"},
Other than that, feel free to stick either/both of these on:
Reviewed-By: Valdis Kletnieks <[email protected]>
Tested-By: Valdis Kletnieks <[email protected]>
Attachment:
pgp50aFnrxvn6.pgp
Description: PGP signature
- Follow-Ups:
- References:
- [PATCH]: proc: export a processes resource limits via proc/<pid>
- From: Neil Horman <[email protected]>
- Re: [PATCH]: proc: export a processes resource limits via proc/<pid>
- From: Neil Horman <[email protected]>
- [PATCH]: proc: export a processes resource limits via proc/<pid>
- Prev by Date: Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
- Next by Date: Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
- Previous by thread: Re: [PATCH]: proc: export a processes resource limits via proc/<pid>
- Next by thread: Re: [PATCH]: proc: export a processes resource limits via proc/<pid>
- Index(es):
 |