linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCHv2 1/2] Export SoC info through sysfs
Date: Fri, 08 Apr 2011 08:41:32 +0100	[thread overview]
Message-ID: <4D9EBC2C.2050809@linaro.org> (raw)
In-Reply-To: <201104080535.02769.arnd@arndb.de>

On 08/04/11 04:35, Arnd Bergmann wrote:
> On Friday 08 April 2011, Greg KH wrote:
>> Symlinks are a requirement as multiple cpus can be attached to a single
>> SoC.
>>
>> What about multiple cpus that are attached to multiple SoCs?  Why even
>> try to describe this relationship, what would userspace get out of this
>> information?
> 
> The only one I can think of is node affinity. I've worked with a system
> (IBM QS2x Cell blade) that had two SoCs with multiple CPUs each. There was
> a significant performance penalty when talking to devices on the remote
> SoC. In that case, we used the NUMA node information in /sys/ to deal
> with it, but we might not want to use the NUMA infrastructure on systems
> that only have RAM on one node.

I'm struggling to see a scenario where we'd have multiple SoCs on a
single device and only one filesystem. ux500 sub-arch code is yet to
facilitate SoC counting functionality. If were are to implement per-SoC
directories would this need to be added?

  reply	other threads:[~2011-04-08  7:41 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 12:35 [RFC PATCHv2 0/2] Export SoC info through sysfs Maxime Coquelin
2011-03-11 12:35 ` [RFC PATCHv2 1/2] " Maxime Coquelin
2011-03-11 13:50   ` Eduardo Valentin
2011-03-11 15:40     ` Maxime Coquelin
2011-03-11 17:35       ` Eduardo Valentin
2011-03-11 14:32   ` Arnd Bergmann
2011-03-11 14:31     ` Eduardo Valentin
2011-03-11 15:40     ` Ben Dooks
2011-03-11 17:38       ` Eduardo Valentin
2011-03-11 15:52     ` Greg KH
2011-03-11 17:58       ` Eduardo Valentin
2011-03-11 19:33         ` Greg KH
2011-03-11 21:42           ` Arnd Bergmann
2011-03-11 22:03             ` Greg KH
2011-03-11 22:13               ` Arnd Bergmann
2011-04-07 16:24                 ` Lee Jones
2011-04-07 21:29                   ` Arnd Bergmann
2011-04-07 21:46                     ` Ryan Mallon
2011-04-07 22:01                       ` Nicolas Pitre
2011-04-07 22:07                         ` Ryan Mallon
2011-04-07 22:45                           ` Nicolas Pitre
2011-04-07 22:56                             ` Ryan Mallon
2011-04-07 23:19                               ` Arnd Bergmann
2011-04-07 23:29                                 ` Greg KH
2011-04-08  3:35                                   ` Arnd Bergmann
2011-04-08  7:41                                     ` Lee Jones [this message]
2011-04-08 15:02                                       ` Arnd Bergmann
2011-04-08 15:43                                         ` Lee Jones
2011-04-08 20:22                                           ` Arnd Bergmann
2011-03-11 12:35 ` [RFC PATCHv2 2/2] ux500: Export U8500 " Maxime Coquelin
2011-03-11 14:11   ` Jean-Christophe PLAGNIOL-VILLARD
2011-03-11 15:20     ` Linus Walleij
2011-03-11 17:24       ` Jean-Christophe PLAGNIOL-VILLARD

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=4D9EBC2C.2050809@linaro.org \
    --to=lee.jones@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).