From owner-freebsd-arch@FreeBSD.ORG Thu Feb 21 03:27:15 2008 Return-Path: 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 D492B16A402; Thu, 21 Feb 2008 03:27:15 +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 C1DAC13C455; Thu, 21 Feb 2008 03:27:15 +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 m1L3RAZK095464; Thu, 21 Feb 2008 03:27:12 GMT (envelope-from davidxu@freebsd.org) Message-ID: <47BCEFDB.5040207@freebsd.org> Date: Thu, 21 Feb 2008 11:28:27 +0800 From: David Xu User-Agent: Thunderbird 2.0.0.9 (X11/20071211) MIME-Version: 1.0 To: Robert Watson References: <20071219211025.T899@desktop> <18311.49715.457070.397815@grasshopper.cs.duke.edu> <20080112182948.F36731@fledge.watson.org> <20080112170831.A957@desktop> <20080112194521.I957@desktop> <20080219234101.D920@desktop> <20080220101348.D44565@fledge.watson.org> <20080220005030.Y920@desktop> <20080220105333.G44565@fledge.watson.org> In-Reply-To: <20080220105333.G44565@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Daniel Eischen , Andrew Gallatin , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Feb 2008 03:27:15 -0000 Robert Watson wrote: > > On Wed, 20 Feb 2008, Jeff Roberson wrote: > >>> So perhaps this means a slightly more complex API, but not much more >>> complex. How about: >>> >>> int cpuaffinity_get(scope, id, length, mask) >>> int cpuaffinity_getmax(scope, id, length, mask) >>> int cpuaffinity_set(scope, id, length, mask) >>> int cpuaffinity_setmax(scope, id, length, mask) >>> Are these features only for jail or something else which don't care CPU L2 cache sharing between cores ? since program still can not figure out L2 sharing information, no way to optimize its thread's cpu arrangement. Regards, David Xu