public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Takayoshi Kochi <t-kochi@bq.jp.nec.com>
Cc: ak@suse.de, steiner@sgi.com, linux-ia64@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Externalize SLIT table
Date: Thu, 04 Nov 2004 06:37:16 +0000	[thread overview]
Message-ID: <20041104063716.GA28895@wotan.suse.de> (raw)
In-Reply-To: <20041104.135721.08317994.t-kochi@bq.jp.nec.com>

On Thu, Nov 04, 2004 at 01:57:21PM +0900, Takayoshi Kochi wrote:
> Hi,
> 
> From: Andi Kleen <ak@suse.de>
> Subject: Re: Externalize SLIT table
> Date: Thu, 4 Nov 2004 05:07:13 +0100
> 
> > > Why not export node_distance() under sysfs?
> > > I like (1).
> > > 
> > > (1) obey one-value-per-file sysfs principle
> > > 
> > > % cat /sys/devices/system/node/node0/distance0
> > > 10
> > 
> > Surely distance from 0 to 0 is 0?
> 
> According to the ACPI spec, 10 means local and other values
> mean ratio to 10.  But what the distance number should mean

Ah, missed that. ok I guess it makes sense to use the same
encoding as ACPI, no need to be intentionally different.

> mean is ambiguous from the spec (e.g. some veondors interpret as
> memory access latency, others interpret as memory throughput
> etc.)
> However relative distance just works for most of uses, I believe.
> 
> Anyway, we should clarify how the numbers should be interpreted
> to avoid confusion.

Defining it as "as defined in the ACPI spec" should be ok. 
I guess even non ACPI architectures will be able to live with that.

Anyways, since we seem to agree and so far nobody has complained
it's just that somebody needs to do a patch?  If possible make
it generic code in drivers/acpi/numa.c, there won't be anything architecture 
specific in this and it should work for x86-64 too.


-Andi

  reply	other threads:[~2004-11-04  6:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-03 20:56 Externalize SLIT table Jack Steiner
2004-11-04  1:59 ` Takayoshi Kochi
2004-11-04  4:07   ` Andi Kleen
2004-11-04  4:57     ` Takayoshi Kochi
2004-11-04  6:37       ` Andi Kleen [this message]
2004-11-05 16:08       ` Jack Steiner
2004-11-05 16:26         ` Andreas Schwab
2004-11-05 16:44           ` Jack Steiner
2004-11-06 11:50             ` Christoph Hellwig
2004-11-06 12:48               ` Andi Kleen
2004-11-06 13:07                 ` Christoph Hellwig
2004-11-05 17:13         ` Erich Focht
2004-11-05 19:13           ` Jack Steiner
2004-11-09 19:23     ` Matthew Dobson
2004-11-04 14:13   ` Jack Steiner
2004-11-04 14:29     ` Andi Kleen
2004-11-04 15:31     ` Erich Focht
2004-11-04 17:04       ` Andi Kleen
2004-11-04 19:36         ` Jack Steiner
2004-11-09 19:45         ` Matthew Dobson
2004-11-09 19:43       ` Matthew Dobson
2004-11-09 20:34         ` Mark Goodwin
2004-11-09 22:00           ` Jesse Barnes
2004-11-09 23:58           ` Matthew Dobson
2004-11-10  5:05             ` Mark Goodwin
2004-11-10 18:45               ` Erich Focht
2004-11-10 22:09                 ` Matthew Dobson
2004-11-18 16:39 ` Jack Steiner

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=20041104063716.GA28895@wotan.suse.de \
    --to=ak@suse.de \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steiner@sgi.com \
    --cc=t-kochi@bq.jp.nec.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