On Fri, Aug 17, 2007 at 12:45:47PM -0700, Andrew Morton wrote: > On Fri, 17 Aug 2007 06:59:18 -0400 > Neil Horman <[EMAIL PROTECTED]> wrote: > > > 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. > > I'm struggling with this a bit. Sure, it _might_ be handy on some > occasions to be able to get at this information. But I've never seen > anyone ask for it before, and it _is_ determinable by other means, if only > strace. > > How do we justify adding yet more stuff to the kernel?
Well, In the past yar and a half I've been asked for it twice. Granted thats not alot of demand, but neither is the code particularly invasive or complex. If your concerned about bloat, my first thought would be to add a compile time config option, which I'm certainly willing to add if the consensus is to do so, but honestly I thought this was small enough that it didnt' really need it. As previously mentioned though, the final say as to what is important enough to make it into the kernel is up to you and Linus. I think this is worthwhile, but if I'm in the minority on that, I'll certainly understand Thanks & Regards Neil -- /*************************************************** *Neil Horman *Software Engineer *Red Hat, Inc. [EMAIL PROTECTED] *gpg keyid: 1024D / 0x92A74FA1 *http://pgp.mit.edu ***************************************************/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
