public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: "Odzioba, Lukasz" <lukasz.odzioba@intel.com>
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 15:26:28 -0700	[thread overview]
Message-ID: <561D8514.2040503@roeck-us.net> (raw)
In-Reply-To: <D6EDEBF1F91015459DB866AC4EE162CC0231739E@IRSMSX103.ger.corp.intel.com>

On 10/13/2015 03:02 PM, Odzioba, Lukasz wrote:
> On Tuesday, October 12, 2015 at 10:32 PM, Guenter Roeck wrote:
>> Why 128 instead of a more reasonable 64 ? What is the required minimum
>> for Xeon Phi ?
>
> It would be fine today, but it will be not enough in 2016 and we would like to
> give GNU/Linux distributions some time to propagate this patch.
> For Knights Corner which is already on the market we need 61.
> For Knights Landing we need 72.

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 ?

Thanks,
Guenter

> For future generation it is not yet public information.
>
>> Also, please consider using the subject line commonly used in hwmon,
>> or at least point to the driver you are changing.
>
> Right, I forgot this time, I'll send another patch just tell me whether 128
> is ok, or please select any other value greater or equal known minimum
> that you think will be more appropriate.
>
> Thanks,
> Lukas
>
>
>


  reply	other threads:[~2015-10-13 22:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 11:53 [PATCH 1/1] Bumps limit of maximum core ID from 32 to 128 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 [this message]
2015-10-13 22:45       ` Odzioba, Lukasz
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=561D8514.2040503@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=fenghua.yu@intel.com \
    --cc=jdelvare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=lukasz.odzioba@intel.com \
    --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