From: "Odzioba, Lukasz" <lukasz.odzioba@intel.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "Yu, Fenghua" <fenghua.yu@intel.com>,
"jdelvare@suse.de" <jdelvare@suse.de>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Phil Pokorny <ppokorny@penguincomputing.com>
Subject: RE: [PATCH 1/1] Bumps limit of maximum core ID from 32 to 128.
Date: Tue, 13 Oct 2015 22:45:16 +0000 [thread overview]
Message-ID: <D6EDEBF1F91015459DB866AC4EE162CC023173BF@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <561D8514.2040503@roeck-us.net>
On Wednesday, October 14, 2015 at 12:26 AM, Guenter Roeck wrote:
> Pardon my ignorance ... those are Xeon Phi processors, and support up to
> 244 threads (for Knights Corner). Programming datasheet isn't easily available,
> so I have to guess a bit. Following the processor numbering scheme of "ordinary"
> processors, the CPU ID can therefore be up to 244 (at least) already today,
> meaning the limit would have to be 256 (assuming that the processor does support
> per-core temperature sensors). On the other side, the public datasheet suggests
> that there are only three temperature sensors.
> What am I missing here ?
Knights Corner can have up to 61 cores with 4 threads per core, so up to 244 threads.
All HT siblings reads temperature from the same core and coretemp driver is aware of it.
That's it needs just one temp_data structure for all threads on given core.
I tested 128 on real HW myself.
Thanks,
Lukas
next prev parent reply other threads:[~2015-10-13 22:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 11:53 Lukasz Odzioba
2015-10-13 20:31 ` Guenter Roeck
2015-10-13 21:05 ` [lm-sensors] " Phil Pokorny
2015-10-13 21:21 ` Guenter Roeck
2015-10-13 22:02 ` Odzioba, Lukasz
2015-10-13 22:26 ` Guenter Roeck
2015-10-13 22:45 ` Odzioba, Lukasz [this message]
2015-10-14 1:17 ` Guenter Roeck
2015-10-14 11:39 ` Odzioba, Lukasz
2015-10-14 14:04 ` Guenter Roeck
2015-10-15 22:08 ` Odzioba, Lukasz
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=D6EDEBF1F91015459DB866AC4EE162CC023173BF@IRSMSX103.ger.corp.intel.com \
--to=lukasz.odzioba@intel.com \
--cc=fenghua.yu@intel.com \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lm-sensors@lm-sensors.org \
--cc=ppokorny@penguincomputing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®