From: Guenter Roeck <linux@roeck-us.net>
To: "Odzioba, Lukasz" <lukasz.odzioba@intel.com>
Cc: "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>,
"Yu, Fenghua" <fenghua.yu@intel.com>
Subject: Re: [lm-sensors] [PATCH 1/1] Bumps limit of maximum core ID from 32 to 128.
Date: Wed, 14 Oct 2015 14:04:00 +0000 [thread overview]
Message-ID: <561E60D0.8040606@roeck-us.net> (raw)
In-Reply-To: <D6EDEBF1F91015459DB866AC4EE162CC02317564@IRSMSX103.ger.corp.intel.com>
On 10/14/2015 04:39 AM, Odzioba, Lukasz wrote:
> On Wednesday, October 14, 2015 at 3:17 AM, Guenter Roeck wrote:
>> Applied, after fixing up the subject and listing the current required limit
>> of 72 cores for Xeon Phi (per published information).
>
> Guenter sorry for inconvenience I forgot that core enumeration on KNL
> is not continuous, so some core ID's are not used. Thus we have to
> change limit to 76 instead of 72.
>
That is just in the comment. The actual limit is still 128.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: "Odzioba, Lukasz" <lukasz.odzioba@intel.com>
Cc: "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>,
"Yu, Fenghua" <fenghua.yu@intel.com>
Subject: Re: [PATCH 1/1] Bumps limit of maximum core ID from 32 to 128.
Date: Wed, 14 Oct 2015 07:04:00 -0700 [thread overview]
Message-ID: <561E60D0.8040606@roeck-us.net> (raw)
In-Reply-To: <D6EDEBF1F91015459DB866AC4EE162CC02317564@IRSMSX103.ger.corp.intel.com>
On 10/14/2015 04:39 AM, Odzioba, Lukasz wrote:
> On Wednesday, October 14, 2015 at 3:17 AM, Guenter Roeck wrote:
>> Applied, after fixing up the subject and listing the current required limit
>> of 72 cores for Xeon Phi (per published information).
>
> Guenter sorry for inconvenience I forgot that core enumeration on KNL
> is not continuous, so some core ID's are not used. Thus we have to
> change limit to 76 instead of 72.
>
That is just in the comment. The actual limit is still 128.
Guenter
next prev parent reply other threads:[~2015-10-14 14:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 11:53 [lm-sensors] [PATCH 1/1] Bumps limit of maximum core ID from 32 to 128 Lukasz Odzioba
2015-10-12 11:53 ` Lukasz Odzioba
2015-10-13 20:31 ` [lm-sensors] " Guenter Roeck
2015-10-13 20:31 ` Guenter Roeck
2015-10-13 21:05 ` [lm-sensors] " Phil Pokorny
2015-10-13 21:05 ` Phil Pokorny
2015-10-13 21:21 ` Guenter Roeck
2015-10-13 21:21 ` Guenter Roeck
2015-10-13 22:02 ` Odzioba, Lukasz
2015-10-13 22:02 ` Odzioba, Lukasz
2015-10-13 22:26 ` [lm-sensors] " Guenter Roeck
2015-10-13 22:26 ` Guenter Roeck
2015-10-13 22:45 ` [lm-sensors] " Odzioba, Lukasz
2015-10-13 22:45 ` Odzioba, Lukasz
2015-10-14 1:17 ` [lm-sensors] " Guenter Roeck
2015-10-14 1:17 ` Guenter Roeck
2015-10-14 11:39 ` [lm-sensors] " Odzioba, Lukasz
2015-10-14 11:39 ` Odzioba, Lukasz
2015-10-14 14:04 ` Guenter Roeck [this message]
2015-10-14 14:04 ` Guenter Roeck
2015-10-15 22:08 ` [lm-sensors] " Odzioba, Lukasz
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=561E60D0.8040606@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 \
/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.