linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: steve.capper@linaro.org (Steve Capper)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 4/4] arm64:numa: adding numa support for arm64 platforms.
Date: Mon, 20 Oct 2014 15:30:46 +0100	[thread overview]
Message-ID: <20141020143045.GA10233@linaro.org> (raw)
In-Reply-To: <20141020142555.GA9968@linaro.org>

On Mon, Oct 20, 2014 at 03:25:56PM +0100, Steve Capper wrote:
> On Fri, Oct 17, 2014 at 10:49:56PM +0530, Ganapatrao Kulkarni wrote:

[...]

>          /*Proximity Distance matrix for 4Node system
> >                        <from-node to-node distance>
> >         */
> >          node-matrix=    <0 0 10>,
> >                                <0 1 20>,
> >                                <0 2 30>,
> >                                <0 3 10>,
> >                                <1 0 20>,
> >                                 <1 1 10>,
> >                                <1 2 30>,
> >                               <1 3 10>,
> >                               <2 0 30>,
> >                               <2 1 20>,
> >                               <2 2 10>,
> >                              <2 3 10>,
> >                             <3 0 10>,
> >                             <3 1 20>,
> >                             <3 2 30>,
> >                             <3 3 10>,
> >  }
> 
> Hi Ganapat,
> The above caught my attention.
> 
> For a 4-node system do we not need 16 distances; the implication of that
> would be that the distance between node A-B could be different from the
> distance between B-A? Also the distance from a node to itself could be
> safely assumed to be zero?
> 
> I think we should have a symmetric matrix with zero-diagonals so strictly
> only seven values would need specifying for a 4-node system.

s/seven/six/

I really need to learn how to count.... :-/

> 
> Cheers,
> -- 
> Steve

  reply	other threads:[~2014-10-20 14:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25  9:03 [RFC PATCH 0/4] arm64:numa: Add numa support for arm64 platforms Ganapatrao Kulkarni
2014-09-25  9:03 ` [RFC PATCH 1/4] arm64: defconfig: increase NR_CPUS range to 2-128 Ganapatrao Kulkarni
2014-10-03 10:58   ` Mark Rutland
2014-10-06  4:29     ` Ganapatrao Kulkarni
2014-09-25  9:03 ` [RFC PATCH 2/4] arm/arm64:dt:numa: adding numa node mapping for memory nodes Ganapatrao Kulkarni
2014-10-03 11:05   ` Mark Rutland
2014-10-06  4:20     ` Ganapatrao Kulkarni
2014-10-06 11:08       ` Mark Rutland
2014-10-06 17:26         ` Ganapatrao Kulkarni
2014-09-25  9:03 ` [RFC PATCH 3/4] arm64:thunder: Add initial dts for Cavium Thunder SoC in 2 Node topology Ganapatrao Kulkarni
2014-10-03 11:19   ` Mark Rutland
2014-09-25  9:03 ` [RFC PATCH 4/4] arm64:numa: adding numa support for arm64 platforms Ganapatrao Kulkarni
2014-10-03 12:13   ` Mark Rutland
2014-10-06  5:14     ` Ganapatrao Kulkarni
2014-10-06 11:26       ` Mark Rutland
2014-10-06 17:52         ` Ganapatrao Kulkarni
2014-10-17 17:19           ` Ganapatrao Kulkarni
2014-10-20 14:25             ` Steve Capper
2014-10-20 14:30               ` Steve Capper [this message]
2014-10-22 11:27                 ` Ganapatrao Kulkarni
2014-10-28  8:48             ` Hanjun Guo
2014-10-29  7:20               ` Ganapatrao Kulkarni
2014-09-25  9:04 ` Ganapatrao Kulkarni

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=20141020143045.GA10233@linaro.org \
    --to=steve.capper@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).