From: David Miller <davem@davemloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH v3] sparc64: Setup sysfs to mark LDOM sockets, cores and threads correctly
Date: Tue, 21 Apr 2015 18:33:52 +0000 [thread overview]
Message-ID: <20150421.143352.745548640287588790.davem@davemloft.net> (raw)
In-Reply-To: <5526cf9b.DFcVpFfcq8CBXHg7%chris.hyser@oracle.com>
From: chris hyser <chris.hyser@oracle.com>
Date: Tue, 21 Apr 2015 14:25:40 -0400
> On 4/16/2015 3:41 PM, David Miller wrote:
>> From: David Miller <davem@davemloft.net>
>> Date: Thu, 09 Apr 2015 19:06:47 -0400 (EDT)
>>> How will this work on T3, T2, and T1 which all neither have the
>>> "socket" mdesc nodes nor level 3 caches?
>>
>> I'm still waiting for you to resolve this Chris.
>>
>> I don't think it's much effort to make this change back down
>> to using the level=2 cache if no level=3 cache is found. Please
>> implement that and resubmit.
>
> So that does appear to work. This is not the patch. I will send that
> out shortly but I thought I'd give you a chance to provide feedback
> while I'm getting that ready.
>
> Here is what I see on a T2.
...
> Diff from the prior patch (I also see some cleanup here I will do):
Yeah that should work just as well on T3 too.
BTW, there are mdesc dumps in my prtconfs repo that you can use
for reference when working on things that walk the mdesc graph.
next prev parent reply other threads:[~2015-04-21 18:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 19:14 [PATCH v3] sparc64: Setup sysfs to mark LDOM sockets, cores and threads correctly chris.hyser
2015-04-09 23:06 ` David Miller
2015-04-10 15:27 ` chris hyser
2015-04-10 19:25 ` David Miller
2015-04-10 19:55 ` chris hyser
2015-04-11 21:57 ` David Miller
2015-04-16 19:41 ` David Miller
2015-04-16 20:31 ` chris hyser
2015-04-21 18:25 ` chris hyser
2015-04-21 18:33 ` David Miller [this message]
2015-04-21 18:39 ` chris hyser
2015-04-21 18:41 ` chris hyser
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=20150421.143352.745548640287588790.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=sparclinux@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 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.