linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: hugh@veritas.com, ak@suse.de, linux-mm@kvack.org
Subject: Re: numa_maps update
Date: Sat, 4 Mar 2006 01:07:08 -0800	[thread overview]
Message-ID: <20060304010708.31697f71.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0603030846170.13932@schroedinger.engr.sgi.com>

Christoph Lameter <clameter@engr.sgi.com> wrote:
>
> Change the format

uh-oh.

> of numa_maps to be more compact and contain additional
> information that is useful for managing and troubleshooting memory on a NUMA
> system. Numa_maps can now also support huge pages.

What will be the userspace impact (ie: breakage) due to this change?

> New items shown:
>
> ... 
> locked
> 	Number of pages locked. Only displayed if >0.

I doubt if the PageLocked() count will be useful.  The only occasion upon
which pages are locked for more than a fleeting period is when they're
initially being brought up to date from backing store - readahead, swapin,
etc.

A more useful statistic would be the number of PageWriteback() pages.

> +	if (file) {
> +
> +		seq_printf(m, " file=");
> +		seq_path(m, file->f_vfsmnt, file->f_dentry, "\n\t");
> +
> +	} else if (vma->vm_start <= mm->brk &&
> +		   vma->vm_end >= mm->start_brk)
> +
> +			seq_printf(m, " heap");
> +
> +	else if (vma->vm_start <= mm->start_stack &&
> +		vma->vm_end >= mm->start_stack)
> +
> +			seq_printf(m, " stack");
> +
> +	if (is_vm_hugetlb_page(vma)) {
> +
> +		check_huge_range(vma, vma->vm_start, vma->vm_end, md);
> +		seq_printf(m, " huge");
> +
> +	} else

What bizarre layout!

--
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:[~2006-03-04  9:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-03 16:58 Christoph Lameter
2006-03-04  9:07 ` Andrew Morton [this message]
2006-03-04  4:59   ` Andi Kleen
2006-03-04 20:08     ` Christoph Lameter
2006-03-04 20:26       ` Andrew Morton
2006-03-06 16:19         ` Christoph Lameter
2006-03-06 17:37         ` Christoph Lameter
2006-03-15  0:01           ` Inconsistent capabilites associated with MPOL_MOVE_ALL Michael Kerrisk
2006-03-15  0:09             ` Christoph Lameter
2006-03-15  0:25               ` Michael Kerrisk
2006-03-15  0:33                 ` Christoph Lameter
2006-03-15  0:40                   ` Michael Kerrisk
2006-03-15  0:41                   ` Andrew Morton
2006-03-15  0:53                     ` Christoph Lameter
2006-03-15  1:01                       ` Andrew Morton
2006-03-15  1:07                         ` Michael Kerrisk
2006-03-15  1:12                           ` Michael Kerrisk
2006-03-15  1:16                             ` Christoph Lameter
2006-03-15  1:08                         ` Christoph Lameter
2006-03-15  0:59                     ` Michael Kerrisk
2006-03-15  1:16                       ` Andrew Morton

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=20060304010708.31697f71.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ak@suse.de \
    --cc=clameter@engr.sgi.com \
    --cc=hugh@veritas.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox