From: Christoph Lameter <clameter@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
linux-mm <linux-mm@kvack.org>,
mel@skynet.ie, y-goto@jp.fujitsu.com,
Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Eric Whitney <eric.whitney@hp.com>
Subject: Re: [PATCH/RFC] Add node 'states' sysfs class attribute - V2
Date: Mon, 27 Aug 2007 22:15:23 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0708272210210.9748@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070827201822.2506b888.akpm@linux-foundation.org>
On Mon, 27 Aug 2007, Andrew Morton wrote:
> > The masks can get quite ugly to read if you have lots of nodes. F.e. with
> > 1024 nodes you get a line that wraps around more than 10 times.
>
> So don't read them - use a program to turn them into your preferred
> human-readable representation.
You are volunterring to write all the programs we need for this and that
debugging situation? Even if you do this: It will significantly slow us
down always having to come to you and ask you for a tool.
> We see this often, btw. People want nice and easy-to-read kernel->human
> interfaces because the tool of choice for displaying these things to humans
> is "cat". How lame is that?
>
> I do think that a sysfs interface like this should be optimised for
> kernel->program communication, not for kernel->human.
Well I keep ending up cat this and that proc entry for debugging and its
difficult to do if one sysfs file spews huge amounts of illegible binary
data to you.
I do not think that tools would have trouble deciphering that format. It
is going to be more compact and easier to handle to have the node ranges
rather than converting a list of binaries. Lee already noted the
huge amounts of zeros that he got.
> > > OK, well if the meminfo file is the only one in there which broke the
> > > golden rule, I don't think we have sufficient excuse to break it again.
> > >
> > > $ cat /sys/devices/system/node/possible
> > > 0-4
> > > $
> > >
> > > I think a bitmap would be better, personally.
> > >
> > > That in fact makes "possible" unneeded, doesn't it? It would always be
> > > all-ones?
> >
> > There could be the case that nodes 1-9 and 20-29 are possible but
> > the ones in between are not available.
>
> OK.
>
> How do we communicate to userspace what is the maximum number of nodes
> which this kernel supports? That would be (1<<CONFIG_NODES_SHIFT), I
> guess. Or maybe we don't care?
The last node mentioned in possible is the highest. That will be difficult
to see if you want the kernel developers to read binary numbers but I
guess we have to be tough.
--
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>
next prev parent reply other threads:[~2007-08-28 5:15 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200708242228.l7OMS5fU017948@imap1.linux-foundation.org>
2007-08-27 15:58 ` [PATCH] 2.6.23-rc3-mm1 - update N_HIGH_MEMORY node state for memory hotadd Lee Schermerhorn
2007-08-27 17:48 ` [PATCH/RFC] Add node 'states' sysfs class attribute Lee Schermerhorn
2007-08-27 19:11 ` Christoph Lameter
2007-08-27 20:08 ` Lee Schermerhorn
2007-08-27 20:15 ` Christoph Lameter
2007-08-27 21:02 ` [PATCH/RFC] Add node 'states' sysfs class attribute - V2 Lee Schermerhorn
2007-08-27 21:04 ` Christoph Lameter
2007-08-28 0:01 ` Andrew Morton
2007-08-28 0:08 ` Christoph Lameter
2007-08-28 1:14 ` Andrew Morton
2007-08-28 1:29 ` Christoph Lameter
2007-08-28 3:18 ` Andrew Morton
2007-08-28 5:15 ` Christoph Lameter [this message]
2007-08-28 5:29 ` Andrew Morton
2007-08-28 5:34 ` Andrew Morton
2007-08-28 5:53 ` Christoph Lameter
2007-08-28 6:12 ` Andrew Morton
2007-08-28 14:05 ` Lee Schermerhorn
2007-08-28 22:02 ` Christoph Lameter
2007-08-28 22:13 ` Nish Aravamudan
2007-08-29 14:43 ` Lee Schermerhorn
2007-08-29 17:39 ` Christoph Lameter
2007-08-29 21:31 ` [PATCH/RFC] Add node states sysfs class attributeS - V3 Lee Schermerhorn
2007-08-29 22:14 ` Christoph Lameter
2007-08-30 13:34 ` Lee Schermerhorn
2007-08-29 22:36 ` Nish Aravamudan
2007-08-30 15:19 ` [PATCH/RFC] Add node states sysfs class attributeS - V4 Lee Schermerhorn
2007-08-30 16:44 ` Nish Aravamudan
2007-08-30 18:20 ` Christoph Lameter
2007-08-30 18:19 ` Christoph Lameter
2007-08-30 18:41 ` Lee Schermerhorn
2007-09-11 13:56 ` [PATCH/RFC] Add node states sysfs class attributeS - V5 Lee Schermerhorn
2007-09-11 20:25 ` Christoph Lameter
2007-09-14 10:50 ` Andrew Morton
2007-09-14 11:35 ` Andy Whitcroft
2007-09-14 14:34 ` Lee Schermerhorn
2007-09-14 14:43 ` Mel Gorman
2007-09-14 15:00 ` Paul Mundt
2007-09-16 12:10 ` Mel Gorman
2007-09-14 16:00 ` Martin J. Bligh
2007-08-28 19:34 ` [PATCH/RFC] Add node 'states' sysfs class attribute - V2 Christoph Lameter
2007-08-28 1:16 ` Yasunori Goto
2007-08-28 1:21 ` Yasunori Goto
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=Pine.LNX.4.64.0708272210210.9748@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=eric.whitney@hp.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mel@skynet.ie \
--cc=y-goto@jp.fujitsu.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