public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	torvalds@linuxfoundation.org, akpm@linuxfoundation.org,
	linux-kernel@vger.kernel.org,
	Dave Hansen <dave@linux.vnet.ibm.com>
Subject: Re: *sigh* /proc/*/pagemap
Date: Mon, 07 Jul 2008 13:51:05 -0500	[thread overview]
Message-ID: <1215456665.11311.179.camel@calx> (raw)
In-Reply-To: <alpine.LFD.1.10.0807071130540.11076@woody.linux-foundation.org>


On Mon, 2008-07-07 at 11:34 -0700, Linus Torvalds wrote:
> 
> On Mon, 7 Jul 2008, Matt Mackall wrote:
> > 
> > It exists to make the VM stop being a big black box. Before now the VM
> > exposed little beyond statistics, many of which are basically
> > meaningless (RSS?). With pagemap, you can actually see precisely where
> > things are getting allocated, how they're getting shared, etc. Think
> > NUMA, think cell phones.
> 
> Umm. How about setting it under CONFIG_DEBUG_VM or something like that 
> then?

I'm certainly not suggesting it's only or even primarily for NUMA or
embedded, just -most obviously- useful for them. Fact is, people have
been interested enough in this POS that I've been getting patches from
all over. Nor is it about debugging the VM, per se. It's about having
transparency in a critical area of the kernel. What pages of my browser
are never swapped in? What is the memory footprint of my forking server,
really? Why the hell can't I get a huge page? Etc.

> Right now it's not even _asked_ about, unless you're EMBEDDED, and 
> defaults to 'y'. Which means that it has all the downsides, an none of the 
> upsides, for 99.99% of all users.

That's what I'd done originally (it's certainly -my- inclination).
Various people (Rusty comes to mind) convinced me to go the other way.

-- 
Mathematics is the supreme nostalgia of our time.


      reply	other threads:[~2008-07-07 18:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-05  1:07 *sigh* /proc/*/pagemap Alexey Dobriyan
2008-07-05  1:53 ` Andrew Morton
2008-07-05  7:44   ` Alexey Dobriyan
2008-07-05  8:02     ` Andrew Morton
     [not found]     ` <28fa9c5e0807161906q68411e9bn5975dc277f67b086@mail.gmail.com>
2008-07-17 20:17       ` Alexey Dobriyan
2008-07-05 17:40   ` Linus Torvalds
2008-07-07 18:23     ` Matt Mackall
2008-07-07 18:34       ` Linus Torvalds
2008-07-07 18:51         ` Matt Mackall [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=1215456665.11311.179.camel@calx \
    --to=mpm@selenic.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=akpm@linuxfoundation.org \
    --cc=dave@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=torvalds@linuxfoundation.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