From owner-freebsd-arch@FreeBSD.ORG  Mon Dec 24 01:43:03 2007
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: arch@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 2BAB416A41B;
	Mon, 24 Dec 2007 01:43:03 +0000 (UTC)
	(envelope-from davidxu@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 3500313C45A;
	Mon, 24 Dec 2007 01:43:03 +0000 (UTC)
	(envelope-from davidxu@FreeBSD.org)
Received: from apple.my.domain (root@localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id lBO1gxND030035;
	Mon, 24 Dec 2007 01:43:01 GMT (envelope-from davidxu@freebsd.org)
Message-ID: <476F0EE5.1040404@freebsd.org>
Date: Mon, 24 Dec 2007 09:44:05 +0800
From: David Xu <davidxu@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.9 (X11/20071211)
MIME-Version: 1.0
To: Robert Watson <rwatson@FreeBSD.org>
References: <20071219211025.T899@desktop> <476B1973.6070902@freebsd.org>
	<20071222183700.L5866@fledge.watson.org>
In-Reply-To: <20071222183700.L5866@fledge.watson.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: arch@FreeBSD.org
Subject: Re: Linux compatible setaffinity.
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Dec 2007 01:43:03 -0000

Robert Watson wrote:
> On Fri, 21 Dec 2007, David Xu wrote:
> 
>> I don't say no to these interfaces, but there is a need to tell user 
>> which cpus are sharing cache, or memory distance is closest enough, 
>> and which cpus are servicing interrupts, e.g, network interrupt and 
>> disks etc, etc, otherwise, blindly setting cpu affinity mask only can 
>> shoot itself in the foot.
> 
> While the Mac OS X API is pretty Mach-specific, it's worth taking a look 
> at their recently-announced affinity API:
> 
> http://developer.apple.com/releasenotes/Performance/RN-AffinityAPI/index.html 
> 
> 
> Robert N M Watson
> Computer Laboratory
> University of Cambridge
> 


I like the interfaces, it is more flexible.

Thanks
David Xu