All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Steiner <steiner@sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: Erich Focht <efocht@hpce.nec.com>,
	Takayoshi Kochi <t-kochi@bq.jp.nec.com>,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Externalize SLIT table
Date: Thu, 04 Nov 2004 19:36:29 +0000	[thread overview]
Message-ID: <20041104193629.GA22887@sgi.com> (raw)
In-Reply-To: <20041104170435.GA19687@wotan.suse.de>

On Thu, Nov 04, 2004 at 06:04:35PM +0100, Andi Kleen wrote:
> On Thu, Nov 04, 2004 at 04:31:42PM +0100, Erich Focht wrote:
> > On Thursday 04 November 2004 15:13, Jack Steiner wrote:
> > > I think it would also be useful to have a similar cpu-to-cpu distance
> > > metric:
> > > ????????% cat /sys/devices/system/cpu/cpu0/distance
> > > ????????10 20 40 60 
> > > 
> > > This gives the same information but is cpu-centric rather than
> > > node centric.
> > 
> > I don't see the use of that once you have some way to find the logical
> > CPU to node number mapping. The "node distances" are meant to be
> 
> I think he wants it just to have a more convenient interface,
> which is not necessarily a bad thing.  But then one could put the 
> convenience into libnuma anyways.
> 
> -Andi

Yes, strictly convenience.  Most of the cases that I have seen deal with
cpu placement & cpu distances from each other. I agree that cpu-to-cpu
distances can be determined by converting to nodes & finding the 
node-to-node distance.

A second reason is symmetry. If there is a /sys/devices/system/node/node0/distance
metric, it seems as though there should also be a /sys/devices/system/cpu/cpu0/distance
metric.

-- 
Thanks

Jack Steiner (steiner@sgi.com)          651-683-5302
Principal Engineer                      SGI - Silicon Graphics, Inc.



WARNING: multiple messages have this Message-ID (diff)
From: Jack Steiner <steiner@sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: Erich Focht <efocht@hpce.nec.com>,
	Takayoshi Kochi <t-kochi@bq.jp.nec.com>,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Externalize SLIT table
Date: Thu, 4 Nov 2004 13:36:29 -0600	[thread overview]
Message-ID: <20041104193629.GA22887@sgi.com> (raw)
In-Reply-To: <20041104170435.GA19687@wotan.suse.de>

On Thu, Nov 04, 2004 at 06:04:35PM +0100, Andi Kleen wrote:
> On Thu, Nov 04, 2004 at 04:31:42PM +0100, Erich Focht wrote:
> > On Thursday 04 November 2004 15:13, Jack Steiner wrote:
> > > I think it would also be useful to have a similar cpu-to-cpu distance
> > > metric:
> > > ????????% cat /sys/devices/system/cpu/cpu0/distance
> > > ????????10 20 40 60 
> > > 
> > > This gives the same information but is cpu-centric rather than
> > > node centric.
> > 
> > I don't see the use of that once you have some way to find the logical
> > CPU to node number mapping. The "node distances" are meant to be
> 
> I think he wants it just to have a more convenient interface,
> which is not necessarily a bad thing.  But then one could put the 
> convenience into libnuma anyways.
> 
> -Andi

Yes, strictly convenience.  Most of the cases that I have seen deal with
cpu placement & cpu distances from each other. I agree that cpu-to-cpu
distances can be determined by converting to nodes & finding the 
node-to-node distance.

A second reason is symmetry. If there is a /sys/devices/system/node/node0/distance
metric, it seems as though there should also be a /sys/devices/system/cpu/cpu0/distance
metric.

-- 
Thanks

Jack Steiner (steiner@sgi.com)          651-683-5302
Principal Engineer                      SGI - Silicon Graphics, Inc.



  reply	other threads:[~2004-11-04 19:36 UTC|newest]

Thread overview: 58+ 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  1:59   ` Takayoshi Kochi
2004-11-04  4:07   ` Andi Kleen
2004-11-04  4:07     ` Andi Kleen
2004-11-04  4:57     ` Takayoshi Kochi
2004-11-04  4:57       ` Takayoshi Kochi
2004-11-04  6:37       ` Andi Kleen
2004-11-04  6:37         ` Andi Kleen
2004-11-05 16:08       ` Jack Steiner
2004-11-05 16:08         ` Jack Steiner
2004-11-05 16:26         ` Andreas Schwab
2004-11-05 16:26           ` Andreas Schwab
2004-11-05 16:44           ` Jack Steiner
2004-11-05 16:44             ` Jack Steiner
2004-11-06 11:50             ` Christoph Hellwig
2004-11-06 11:50               ` Christoph Hellwig
2004-11-06 12:48               ` Andi Kleen
2004-11-06 12:48                 ` Andi Kleen
2004-11-06 13:07                 ` Christoph Hellwig
2004-11-06 13:07                   ` Christoph Hellwig
2004-11-05 17:13         ` Erich Focht
2004-11-05 17:13           ` Erich Focht
2004-11-05 19:13           ` Jack Steiner
2004-11-05 19:13             ` Jack Steiner
2004-11-09 19:23     ` Matthew Dobson
2004-11-09 19:23       ` Matthew Dobson
2004-11-04 14:13   ` Jack Steiner
2004-11-04 14:13     ` Jack Steiner
2004-11-04 14:29     ` Andi Kleen
2004-11-04 14:29       ` Andi Kleen
2004-11-04 15:31     ` Erich Focht
2004-11-04 15:31       ` Erich Focht
2004-11-04 17:04       ` Andi Kleen
2004-11-04 17:04         ` Andi Kleen
2004-11-04 19:36         ` Jack Steiner [this message]
2004-11-04 19:36           ` Jack Steiner
2004-11-09 19:45         ` Matthew Dobson
2004-11-09 19:45           ` Matthew Dobson
2004-11-09 19:43       ` Matthew Dobson
2004-11-09 19:43         ` Matthew Dobson
2004-11-09 20:34         ` Mark Goodwin
2004-11-09 20:34           ` Mark Goodwin
2004-11-09 22:00           ` Jesse Barnes
2004-11-09 22:00             ` Jesse Barnes
2004-11-09 23:58           ` Matthew Dobson
2004-11-09 23:58             ` Matthew Dobson
2004-11-10  5:05             ` Mark Goodwin
2004-11-10  5:05               ` Mark Goodwin
2004-11-10 18:45               ` Erich Focht
2004-11-10 18:45                 ` Erich Focht
2004-11-10 22:09                 ` Matthew Dobson
2004-11-10 22:09                   ` Matthew Dobson
2004-11-18 16:39 ` Jack Steiner
2004-11-18 16:39   ` Jack Steiner
     [not found] <20041103205655.GA5084@sgi.com.suse.lists.linux.kernel>
     [not found] ` <20041104.105908.18574694.t-kochi@bq.jp.nec.com.suse.lists.linux.kernel>
     [not found]   ` <20041104040713.GC21211@wotan.suse.de.suse.lists.linux.kernel>
     [not found]     ` <20041104.135721.08317994.t-kochi@bq.jp.nec.com.suse.lists.linux.kernel>
     [not found]       ` <20041105160808.GA26719@sgi.com.suse.lists.linux.kernel>
2004-11-06  6:30         ` Andi Kleen
2004-11-23 17:32           ` Jack Steiner
2004-11-23 19:06             ` Andi Kleen

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=20041104193629.GA22887@sgi.com \
    --to=steiner@sgi.com \
    --cc=ak@suse.de \
    --cc=efocht@hpce.nec.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.