[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081201101245.0a2f3123.randy.dunlap@oracle.com>
Date: Mon, 1 Dec 2008 10:12:45 -0800
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Greg KH <greg@...ah.com>
Cc: Alexey Dobriyan <adobriyan@...il.com>,
Remi Colinet <remi.colinet@...il.com>,
linux-kernel@...r.kernel.org, akpm@...l.org, torvalds@...l.org,
linux-api@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [RESEND][PATCH] Add /proc/mempool to display mempool usage
On Sat, 29 Nov 2008 15:49:07 -0800 Greg KH wrote:
> On Sun, Nov 30, 2008 at 12:42:07AM +0300, Alexey Dobriyan wrote:
> > On Sat, Nov 29, 2008 at 06:44:49PM +0100, Remi Colinet wrote:
> > > This patch add a new /proc/mempool file in order to display mempool usage.
> > >
> > > The feature can be disabled with CONFIG_PROC_MEMPOOL=N during kernel
> > > configuration.
> >
> > We're NOT adding config option per proc file.
> >
> > And can we, please, freeze /proc for not per-process stuff and open debugfs
> > for random stuff, please?
>
> debugfs has been open for random stuff since the day it was added to the
> tree :)
>
> Feel free to put this kind of thing there instead of proc.
Do distros ship with debugfs enabled?
The problem with using debugfs is that it is very optional IMO.
---
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists