linux-numa.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cliff Wickman <cpw@sgi.com>
To: Kornilios Kourtis <kkourt@cslab.ece.ntua.gr>
Cc: Andi Kleen <andi@firstfloor.org>, linux-numa@vger.kernel.org
Subject: Re: find the node that a cpu belongs to
Date: Thu, 19 Mar 2009 09:16:16 -0500	[thread overview]
Message-ID: <20090319141616.GA9810@sgi.com> (raw)
In-Reply-To: <20090317113242.GA30922@solar.cslab.ece.ntua.gr>

Hi Kornilios,

I applied and tested your patch (adding numa_node_of_cpu()).

It looks good.  Thanks.

It is in the numactl-2.0.3-rc2.tar.gz tarball.
(ftp://oss.sgi.com/www/projects/libnuma/download/)

-Cliff
-- 
Cliff Wickman
Silicon Graphics, Inc.
cpw@sgi.com
(651) 683-3824

      parent reply	other threads:[~2009-03-19 14:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17  1:09 find the node that a cpu belongs to Kornilios Kourtis
2009-03-17 10:45 ` Andi Kleen
2009-03-17 11:32   ` Kornilios Kourtis
2009-03-17 11:59     ` Andi Kleen
2009-03-18 15:19       ` Kornilios Kourtis
2009-03-19 14:16     ` Cliff Wickman [this message]

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=20090319141616.GA9810@sgi.com \
    --to=cpw@sgi.com \
    --cc=andi@firstfloor.org \
    --cc=kkourt@cslab.ece.ntua.gr \
    --cc=linux-numa@vger.kernel.org \
    /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).