Re: sched: CPU #1's llc-sibling CPU #0 is not on the same node!

[H. Peter Anvin]

If NUMAQ is breaking real stuff we can kill it by marking it BROKEN.  Rip-out is 3.10 at this stage.

Ingo Molnar <mingo@xxxxxxxxxx> wrote:

>
>* Borislav Petkov <bp@xxxxxxxxx> wrote:
>
>> On Thu, Feb 28, 2013 at 10:37:10PM -0800, H. Peter Anvin wrote:
>> > I'd be very happy to get the NUMAQ code ripped out.  I am wondering
>if
>> > there are any reasons to keep any 32-bit x86 NUMA code at all.
>> 
>> How much would it hurt us if we said 3.8 is the last kernel that
>supported NUMAQ? 
>> If anyone wants the functionality, they should use 3.8 or older.
>
>v3.9 - any non-trivial patch in the stage of being contemplated near
>the end of the 
>v3.9 merge window is most likely v3.10 material.
>
>Thanks,
>
>	Ingo

-- 
Sent from my mobile phone. Please excuse brevity and lack of formatting.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/