[lkml]   [2002]   [Sep]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] "fully HT-aware scheduler" support, 2.5.31-BK-curr

On Tue, 3 Sep 2002, Michael Hohnbaum wrote:

> > (NUMA systems which have tightly coupled CPUs with a smaller cache and
> > protected by a large L3 cache might benefit from sharing the runqueue as
> > well - but the target for this concept is SMT.)
> Sharing a runqueue for all processors on a node of a NUMA system has the
> drawback of not accounting for cache warmth for processes. [...]

hence the 'might'.

> [...] Ideally, for a NUMA system there should continue to be individual
> runqueues per cpu (or per set of HT processors), and then a grouping of
> runqueues at the node level. At load balancing, priority should be to
> redispatch on the same processor, followed by on the same node. The
> pain threshold for crossing the node boundary will vary depending on the
> NUMA-ness of the hardware, so it would be good to account for this in
> the scheduler.



To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.082 / U:0.076 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site