From: Oleg Nesterov <oleg@tv-sign.ru>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: + proc-export-a-processes-resource-limits-via-proc-pid.patch added to -mm tree
Date: Sun, 19 Aug 2007 19:19:50 +0400 [thread overview]
Message-ID: <20070819151950.GA7787@tv-sign.ru> (raw)
In-Reply-To: <20070819130319.GA25178@hmsreliant.think-freely.org>
On 08/19, Neil Horman wrote:
> Copy That
>
> 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.
Looks good, thanks.
Oleg.
prev parent reply other threads:[~2007-08-19 15:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 22:22 Oleg Nesterov
2007-08-18 11:58 ` Neil Horman
2007-08-18 12:59 ` Oleg Nesterov
2007-08-18 18:55 ` Neil Horman
2007-08-18 19:03 ` Oleg Nesterov
2007-08-18 23:23 ` Neil Horman
2007-08-19 8:57 ` Oleg Nesterov
2007-08-19 13:03 ` Neil Horman
2007-08-19 15:19 ` Oleg Nesterov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070819151950.GA7787@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®