public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Dobson <colpatch@us.ibm.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@transmeta.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>, Dave Jones <davej@suse.de>,
	Martin Bligh <mjbligh@us.ibm.com>,
	Andrew Morton <akpm@zip.com.au>, Patrick Mochel <mochel@osdl.org>
Subject: [rfc][patch] DriverFS Topology + per-node (NUMA) meminfo
Date: Mon, 21 Oct 2002 14:37:26 -0700	[thread overview]
Message-ID: <3DB47396.4070505@us.ibm.com> (raw)

Good afternoon,
	Here's I've been sitting on a bit too long.  This patch adds Topology 
information to driverfs, and adds a meminfo file to each node's 
directory which contains: <drum roll> that nodes memory info!
	Pat, I got rid of the per-arch callbacks, since they weren't doing 
anything even remotely useful yet, and they bloated the patch even 
further.  I left in the arch_info pointers so we can put the arch 
specific callbacks back in if anyone wants...  I've also rolled Martin's 
/proc/meminfo.numa patch into this.
	BTW, I have a patch that will changes the usage of 'int numnodes' into 
the more generic 'num_online_nodes()' and 'node_set_online()' calls. 
I'll be sending that patch momentarily also.
	As always: comment, question, and flame away!

Cheers!

-Matt


             reply	other threads:[~2002-10-21 21:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21 21:37 Matthew Dobson [this message]
2002-10-21 21:48 ` [rfc][patch] DriverFS Topology + per-node (NUMA) meminfo Patrick Mochel
2002-10-21 21:50   ` Matthew Dobson
2002-10-28  3:05     ` Rusty Russell
2002-10-28 18:58       ` Matthew Dobson
2002-10-28 23:24         ` Rusty Russell
2002-10-29  1:08           ` Matthew Dobson
2002-10-29  3:09             ` Rusty Russell

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=3DB47396.4070505@us.ibm.com \
    --to=colpatch@us.ibm.com \
    --cc=akpm@zip.com.au \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjbligh@us.ibm.com \
    --cc=mochel@osdl.org \
    --cc=torvalds@transmeta.com \
    /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