public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@sgi.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] patch to /proc/meminfo to display NUMA stats
Date: Mon, 22 Apr 2002 16:49:25 -0700	[thread overview]
Message-ID: <20020422234925.GA1173212@sgi.com> (raw)
In-Reply-To: <25270000.1019495119@flay> <6087.1019518771@ocs3.intra.ocs.com.au>

I implemented something kind of like this for the discontig project,
but I called it /proc/discontig.  The patch just walked all the
pgdata_t structures and did its best to find out where the memory was
being used.  See http://sourceforge.net/projects/discontig for the
patch.  The first column of the output should probably be called
'region' or something, since it's not NUMA specific at all...

Jesse

On Tue, Apr 23, 2002 at 09:39:31AM +1000, Keith Owens wrote:
> On Mon, 22 Apr 2002 10:05:19 -0700, 
> "Martin J. Bligh" <Martin.Bligh@us.ibm.com> wrote:
> >Below is a patch to /proc/meminfo to display free, used and total
> >memory per node on a NUMA machine. It works fine on an ia32
> >machine, but is not yet ready for submission until I make it generic.
> >Before I go to the effort of doing that, I thought I'd seek some feedback.
> >
> >diff -urN virgin-2.4.18/fs/proc/proc_misc.c linux-2.4.18-meminfo/fs/proc/proc_misc.c
> >--- virgin-2.4.18/fs/proc/proc_misc.c	Tue Nov 20 21:29:09 2001
> >+++ linux-2.4.18-meminfo/fs/proc/proc_misc.c	Mon Apr 15 09:31:32 2002
> >+#ifdef CONFIG_NUMA
> >+	for (nid = 0; nid < numnodes; ++nid) {
> >+		si_meminfo_node(&i, nid);
> >+		len += sprintf(page+len, "\n"
> >+			"Node %d MemTotal:     %8lu kB\n"
> >+			"Node %d MemFree:     %8lu kB\n"
> >+			"Node %d MemUsed:     %8lu kB\n"
> >+			"Node %d HighTotal:    %8lu kB\n"
> >+			"Node %d HighFree:     %8lu kB\n"
> >+			"Node %d LowTotal:     %8lu kB\n"
> >+			"Node %d LowFree:      %8lu kB\n",
> >+			nid, K(i.totalram),
> >+			nid, K(i.freeram),
> >+			nid, K(i.totalram-i.freeram),
> >+			nid, K(i.totalhigh),
> >+			nid, K(i.freehigh),
> >+			nid, K(i.totalram-i.totalhigh),
> >+			nid, K(i.freeram-i.freehigh));
> >+	}
> >+#endif

      reply	other threads:[~2002-04-23 17:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-22 17:05 [RFC] patch to /proc/meminfo to display NUMA stats Martin J. Bligh
2002-04-22 16:39 ` Christoph Hellwig
2002-04-24 19:39   ` Martin J. Bligh
2002-04-24 19:47     ` Martin J. Bligh
2002-04-22 23:39 ` Keith Owens
2002-04-22 23:49   ` Jesse Barnes [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=20020422234925.GA1173212@sgi.com \
    --to=jbarnes@sgi.com \
    --cc=Martin.Bligh@us.ibm.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