Re: x86: Convert cpu_core_map to be a per cpu variable

From: Christoph Lameter <[email protected]>
Date: Fri, 13 Jul 2007 09:34:02 -0700 (PDT)

> But the code modified here is x86_64 and i386 specific? Is there an 
> overlap?

I see, the acessor is abstracted via a function.

That seems pointless, and allows you to do things like this, improving
the implementation on one set of platforms yet leave others using
SMT/multi-core scheduling behind.

It makes a lot more sense to make the implementation consistent
and therefore the improvements are seen on every platform.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: x86: Convert cpu_core_map to be a per cpu variable
    • From: Christoph Lameter <[email protected]>

• References:
  • x86: Convert cpu_core_map to be a per cpu variable
    • From: Christoph Lameter <[email protected]>
  • Re: x86: Convert cpu_core_map to be a per cpu variable
    • From: David Miller <[email protected]>
  • Re: x86: Convert cpu_core_map to be a per cpu variable
    • From: Christoph Lameter <[email protected]>

• Prev by Date: Re: [PATCH 0/3][try 1] init: enable system-on-initramfs
• Next by Date: Re: e100 PCI bridge problem
• Previous by thread: Re: x86: Convert cpu_core_map to be a per cpu variable
• Next by thread: Re: x86: Convert cpu_core_map to be a per cpu variable
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]