linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russ Anderson <rja@sgi.com>
To: haveblue@us.ibm.com (Dave Hansen)
Cc: rja@sgi.com (Russ Anderson),
	rmk+lkml@arm.linux.org.uk (Russell King),
	linux-kernel@vger.kernel.org (Linux Kernel Mailing List)
Subject: Re: [RFC] Linux memory error handling
Date: Wed, 15 Jun 2005 16:27:57 -0500 (CDT)	[thread overview]
Message-ID: <200506152127.j5FLRvvl1466135@clink.americas.sgi.com> (raw)
In-Reply-To: <1118868302.6620.34.camel@localhost> from "Dave Hansen" at Jun 15, 2005 01:45:02 PM

Dave Hansen wrote:
> On Wed, 2005-06-15 at 15:28 -0500, Russ Anderson wrote:
> > Russell King wrote:
> > > On Wed, Jun 15, 2005 at 04:26:13PM +0100, Maciej W. Rozycki wrote:
> > > > On Wed, 15 Jun 2005, Russ Anderson wrote:
> > > > > 	Memory DIMM information & settings:
> > > > > 
> > > > > 	    Use a /proc/dimm_info interface to pass DIMM information to Linux.
> > > > > 	    Hardware vendors could add their hardware specific settings.
> > > > 
> > > >  I'd recommend a more generic name rather than "dimm_info" if that is to 
> > > > be reused universally.
> > > 
> > I really don't care what it's called, as long as it's descriptive.
> > /proc/meminfo is taken.  :-)
> > 
> > One idea would follow the concept of /proc/bus/ and have /proc/memory/
> > with different memory types.  /proc/memory/dimm0 /proc/memory/dimm1
> > /proc/memory/flash0 .  
> 
> Please don't do this in /proc.  If it's a piece of hardware, and it
> needs to have some information about it exported, then you need to use
> kobjects and sysfs.  

How about /sys/devices/system/memory/dimmX with links in
/sys/devices/system/node/nodeX/ ?  Does that sound better?


-- 
Russ Anderson, OS RAS/Partitioning Project Lead  
SGI - Silicon Graphics Inc          rja@sgi.com

  reply	other threads:[~2005-06-15 21:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15 14:30 [RCF] Linux memory error handling Russ Anderson
2005-06-15 15:08 ` Andi Kleen
2005-06-15 16:36   ` Russ Anderson
2005-06-15 15:26 ` Maciej W. Rozycki
2005-06-15 19:46   ` Russell King
2005-06-15 20:28     ` [RFC] " Russ Anderson
2005-06-15 20:45       ` Dave Hansen
2005-06-15 21:27         ` Russ Anderson [this message]
2005-06-15 21:33           ` Dave Hansen
2005-06-20 20:42             ` Russ Anderson
2005-06-20 21:07               ` Dave Hansen
2005-06-15 22:09   ` Russ Anderson
2005-06-16 19:42     ` Maciej W. Rozycki
2005-06-16  1:03   ` [RCF] " Ross Biro
2005-06-15 20:42 ` Joel Schopp
2005-06-16  2:54 ` Wang, Zhenyu

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=200506152127.j5FLRvvl1466135@clink.americas.sgi.com \
    --to=rja@sgi.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).