From: Martin Rogge <marogge@onlinehome.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux thread scheduling
Date: Fri, 10 Feb 2012 23:44:12 +0100
User-Agent: KMail/1.13.6 (Linux/3.2.4-ck1; KDE/4.5.5; x86_64; ; )
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-Id: <201202102344.12509.marogge@onlinehome.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1117
Lines: 24

Xin Tong wrote:

> I have a program that spawns 3 threads and there is a great deal of
> sharing among the three threads. they all read/update a couple of
> shared variables.
> 
> I run this on nehalem (8 cores, 4 core in each physical package),  I
> find that running the 3 threads on core 0, 1, 2 (using
> pthread_setaffinitiy) gives much better results, this is because the
> cache coherency protocol performs much better on the same package.
> However, if  I leave Linux (Suse Enterprise) to schedule it. it gives
> much worse performance, i suspect that linux is scheduling the 3
> threads across the physical packages ( 2 on one package, 1 on
> another). Is this possible ? why does linux do this ?

the following paper on cpu schedulers was posted recently. Maybe it gives you 
a starting point.

http://research.cs.wisc.edu/wind/Publications/meehean-thesis11.html
--
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/