public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Remi Colinet <remi.colinet@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
	Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND][PATCH] Add /proc/mempool to display mempool usage
Date: Sun, 30 Nov 2008 22:00:11 +0100	[thread overview]
Message-ID: <1228078811.2658.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20081129234907.GA2340@kroah.com>

On Sat, 2008-11-29 at 15:49 -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.
> 

Acknowledged,

> thanks,
> 
> greg k-h

Thanks,
Remi


  reply	other threads:[~2008-11-30 21:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-29 17:44 [RESEND][PATCH] Add /proc/mempool to display mempool usage Remi Colinet
2008-11-29 21:42 ` Alexey Dobriyan
2008-11-29 23:49   ` Greg KH
2008-11-30 21:00     ` Remi Colinet [this message]
2008-12-01 18:12     ` Randy Dunlap
2008-12-01 19:13       ` Matt Mackall
2008-12-01 20:02         ` Andrew Morton
2008-12-01 20:07           ` Pekka Enberg
2008-12-01 20:12             ` Linus Torvalds
2008-12-01 20:23               ` Linus Torvalds
2008-12-01 22:02               ` Pekka Enberg
2008-12-01 22:20                 ` Matt Mackall
2008-12-02  2:54                 ` Linus Torvalds
2008-12-04 16:02                   ` Michael Kerrisk

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=1228078811.2658.2.camel@localhost.localdomain \
    --to=remi.colinet@gmail.com \
    --cc=adobriyan@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    /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