mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nakajima, Jun" <jun.nakajima@intel.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] hyper-threading information in /proc/cpuinfo
Date: Mon, 28 Oct 2002 14:36:31 -0800	[thread overview]
Message-ID: <F2DBA543B89AD51184B600508B68D4000ECE76E2@fmsmsx103.fm.intel.com> (raw)

Looks like they don't want us to use "threads" for various reasons. Those
could be even religious/branding issues, which I have no interests in. My
interest is to have consistent format/info for HT cpuinfo among the kernels.

So can you please change like:

+#ifdef CONFIG_SMP
+	if (cpu_has_ht) {
+		seq_printf(m, "physical id\t: %d\n", phys_proc_id[n]);
+		seq_printf(m, "logical cpus\t: %d per package\n",
smp_num_siblings);
+	}
+#endif

This is consistent with the spec/manual from Intel. They use logical
processor (and thread :-), physical processor, physical package, etc.

Thanks,
Jun

-----Original Message-----
From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk]
Sent: Friday, October 25, 2002 3:15 PM
To: Nakajima, Jun
Cc: Robert Love; 'Dave Jones'; 'akpm@digeo.com';
'linux-kernel@vger.kernel.org'; 'chrisl@vmware.com'; 'Martin J. Bligh'
Subject: RE: [PATCH] hyper-threading information in /proc/cpuinfo


On Fri, 2002-10-25 at 22:50, Nakajima, Jun wrote:
> Sorry,
> 
> Can you please change "siblings\t" to "threads\t\t". SuSE 8.1, for
example,
> is already doing it:

Could do
> 
> +#ifdef CONFIG_SMP
> +	if (cpu_has_ht) {
> +		seq_printf(m, "physical id\t: %d\n", phys_proc_id[n]);
> +		seq_printf(m, "threads\t\t: %d\n", smp_num_siblings);
> +	}
> +#endif


Im just wondering what we would then use to describe a true multiple cpu
on a die x86. Im curious what the powerpc people think since they have
this kind of stuff - is there a generic terminology they prefer ?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

             reply	other threads:[~2002-10-28 22:30 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-28 22:36 Nakajima, Jun [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-26  1:58 Nakajima, Jun
2002-10-26  0:54 Nakajima, Jun
2002-10-26  0:26 Nakajima, Jun
2002-10-25 23:59 Nakajima, Jun
2002-10-26  0:43 ` J.A. Magallon
2002-10-26  0:47   ` J.A. Magallon
2002-10-26  2:51     ` Martin J. Bligh
2002-10-26 19:48   ` Rik van Riel
2002-10-28 18:53     ` chrisl
2002-10-28 21:54       ` J.A. Magallon
2002-10-25 23:24 Nakajima, Jun
2002-10-25 23:45 ` Jeff Garzik
2002-10-25 22:42 Nakajima, Jun
2002-10-25 22:57 ` Jeff Garzik
2002-10-25 23:21   ` David D. Hagood
2002-10-25 23:25     ` Robert Love
2002-10-25 23:45       ` David D. Hagood
2002-10-26  0:37         ` Robert Love
2002-10-25 23:51 ` Daniel Phillips
2002-10-25 21:50 Nakajima, Jun
2002-10-25 21:54 ` Robert Love
2002-10-25 22:19   ` chrisl
2002-10-25 22:14 ` Alan Cox
2002-10-25 22:06   ` Daniel Phillips
2002-10-25 22:10     ` Robert Love
2002-10-25 22:25       ` Jeff Garzik
2002-10-26  0:49   ` Rik van Riel
2002-10-26 15:45   ` Eric W. Biederman
2002-10-25 20:38 [PATCH] How to get number of physical CPU in linux from user space? Nakajima, Jun
2002-10-25 21:30 ` [PATCH] hyper-threading information in /proc/cpuinfo Robert Love
2002-10-25 21:39   ` Robert Love
2002-10-26  0:01   ` Dave Jones
2002-10-26  0:04     ` Jeff Garzik
2002-10-26  0:12       ` Dave Jones
2002-10-26  0:16         ` Jeff Garzik
2002-10-26  0:33           ` Robert Love

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=F2DBA543B89AD51184B600508B68D4000ECE76E2@fmsmsx103.fm.intel.com \
    --to=jun.nakajima@intel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@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 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®