Messages in this thread | | | Subject | Re: [PATCH] hyper-threading information in /proc/cpuinfo | From | (Eric W. Biederman) | Date | 26 Oct 2002 09:45:18 -0600 |
| |
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> 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 ?
How about using "SMT width" for the P4 case? And if we needed to break it down per package for a Power4 and the like we could talk about CMP something, or other.
Only SMT and CMP seem to be unambiguous prefixes. Though for CMP we probably do not need to do anything because it really is 2 cpus, and we only need to worry about locatity in the cache hierarchy not the fact that if we schedule a cpu intensive job on 1 ``cpu'' the others are useless.
Eric - 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/
| |