From owner-freebsd-current@FreeBSD.ORG  Tue Feb 26 02:21:46 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id D33C316A401
	for <current@freebsd.org>; Tue, 26 Feb 2008 02:21:46 +0000 (UTC)
	(envelope-from jroberson@chesapeake.net)
Received: from webaccess-cl.virtdom.com (webaccess-cl.virtdom.com
	[216.240.101.25])
	by mx1.freebsd.org (Postfix) with ESMTP id 9B34A13C447
	for <current@freebsd.org>; Tue, 26 Feb 2008 02:21:46 +0000 (UTC)
	(envelope-from jroberson@chesapeake.net)
Received: from [192.168.1.107] (cpe-24-94-75-93.hawaii.res.rr.com
	[24.94.75.93]) (authenticated bits=0)
	by webaccess-cl.virtdom.com (8.13.6/8.13.6) with ESMTP id
	m1Q2LihK009816
	for <current@freebsd.org>; Mon, 25 Feb 2008 21:21:45 -0500 (EST)
	(envelope-from jroberson@chesapeake.net)
Date: Mon, 25 Feb 2008 16:23:22 -1000 (HST)
From: Jeff Roberson <jroberson@chesapeake.net>
X-X-Sender: jroberson@desktop
To: current@freebsd.org
Message-ID: <20080225161855.M920@desktop>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: 
Subject: Topology aware scheduling algorithm.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2008 02:21:46 -0000

Also in the cpuset.diff at:

http://people.freebsd.org/~jeff/cpuset.diff

There is support for cpu topology aware scheduling.  This allows the 
scheduler to know which cores are colocated on packages and what the cache 
arrangement between them is.

We have seen big improvements in some workloads and some reduction in 
other workloads.  However, I believe this should finally close the gap on 
the few benchmarks where ULE could trail 4BSD.  Please prove me wrong if 
you can so I can continue to make ULE better.

Right now the MD code is slightly lagging behind what the scheduler can 
utilize.  If you have an interest in digging through processor 
documentation to write code to detect more information about the caches 
please contact me.  I'd love some help.

This code and the cpusets will likely be committed to 8.0 by the end of 
the week and then we'll discuss MFCs after some time to settle there.

Thanks,
Jeff