Re: [PATCH][RFC] make cpu_sibling_map a cpumask_t
From: Ingo Molnar (mingo_at_redhat.com)
Date: 12/09/03
- Previous message: Nick Piggin: "Re: [PATCH][RFC] make cpu_sibling_map a cpumask_t"
- In reply to: Nick Piggin: "Re: [PATCH][RFC] make cpu_sibling_map a cpumask_t"
- Next in thread: Nick Piggin: "Re: [PATCH][RFC] make cpu_sibling_map a cpumask_t"
- Reply: Nick Piggin: "Re: [PATCH][RFC] make cpu_sibling_map a cpumask_t"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 8 Dec 2003 18:36:28 -0500 (EST) To: Nick Piggin <piggin@cyberone.com.au>
the thing that makes balancing-only driven SMT possible with current 2.6.0
is the overbalancing we do (to have cross-CPU fairness). Previous
iterations of the O(1) scheduler (all the 2.4 backports) didnt do this so
all the add-on SMT schedulers tended to have a problem achieving good SMT
distribution. Now that we more agressively balance, this isnt such a big
issue anymore.
so i tend to lean towards your SMT patch, it's much easier to maintain
than my runqueue-sharing approach. The performance is equivalent as far as
i can see (around 20%, and a stabilization of the distribution of
runtimes) - but please also boot my patch and repeat the exact same
measurements you did.
Ingo
-
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/
- Previous message: Nick Piggin: "Re: [PATCH][RFC] make cpu_sibling_map a cpumask_t"
- In reply to: Nick Piggin: "Re: [PATCH][RFC] make cpu_sibling_map a cpumask_t"
- Next in thread: Nick Piggin: "Re: [PATCH][RFC] make cpu_sibling_map a cpumask_t"
- Reply: Nick Piggin: "Re: [PATCH][RFC] make cpu_sibling_map a cpumask_t"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|