All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Howard Chu <hyc@symas.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: swap map
Date: Tue, 30 Jan 2007 11:20:24 +0000	[thread overview]
Message-ID: <20070130112024.GA18705@infradead.org> (raw)
In-Reply-To: <45BF2823.2090005@symas.com>

On Tue, Jan 30, 2007 at 03:12:35AM -0800, Howard Chu wrote:
> In the it-would-be-nice department... While I was twiddling with swappiness 
> and benchmarking some code, I thought it would be pretty cool if there was 
> a node in /proc/<pid> that would show which pages of a process are resident 
> or nonresident. I'm not sure that it would be useful very often, but I was 
> thinking one could get a snapshot of that, correlated with traces from a 
> malloc profiler, to show what portions of a program's memory usage was in 
> active use vs idle.

That's be a remote mincore().  This should be more or less trivial,
do_mincore would need a mm_struct argument instead of always using
current->mm and we'd need a simple seq_file interface iterating over it.

Any volunteers?

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Howard Chu <hyc@symas.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: swap map
Date: Tue, 30 Jan 2007 11:20:24 +0000	[thread overview]
Message-ID: <20070130112024.GA18705@infradead.org> (raw)
In-Reply-To: <45BF2823.2090005@symas.com>

On Tue, Jan 30, 2007 at 03:12:35AM -0800, Howard Chu wrote:
> In the it-would-be-nice department... While I was twiddling with swappiness 
> and benchmarking some code, I thought it would be pretty cool if there was 
> a node in /proc/<pid> that would show which pages of a process are resident 
> or nonresident. I'm not sure that it would be useful very often, but I was 
> thinking one could get a snapshot of that, correlated with traces from a 
> malloc profiler, to show what portions of a program's memory usage was in 
> active use vs idle.

That's be a remote mincore().  This should be more or less trivial,
do_mincore would need a mm_struct argument instead of always using
current->mm and we'd need a simple seq_file interface iterating over it.

Any volunteers?

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2007-01-30 11:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30 11:12 swap map Howard Chu
2007-01-30 11:20 ` Christoph Hellwig [this message]
2007-01-30 11:20   ` Christoph Hellwig
2007-01-30 11:33   ` Nick Piggin
2007-01-30 11:33     ` Nick Piggin

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=20070130112024.GA18705@infradead.org \
    --to=hch@infradead.org \
    --cc=hyc@symas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.