From owner-freebsd-smp@FreeBSD.ORG Fri Feb 23 21:18:36 2007 Return-Path: X-Original-To: freebsd-smp@freebsd.org Delivered-To: freebsd-smp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7758316A407; Fri, 23 Feb 2007 21:18:36 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 355EC13C4B7; Fri, 23 Feb 2007 21:18:36 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.14.0/8.14.0/NETPLEX) with ESMTP id l1NLIXIn008700; Fri, 23 Feb 2007 16:18:33 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (mail.ntplx.net [204.213.176.10]); Fri, 23 Feb 2007 16:18:33 -0500 (EST) Date: Fri, 23 Feb 2007 16:18:33 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Julian Elischer In-Reply-To: <45DF4CBA.1010906@elischer.org> Message-ID: References: <07DDDFCFB8BE0A43BCA52E743373DBDC030C5D5A@orsmsx416.amr.corp.intel.com> <20070223151158.Q88189@fledge.watson.org> <07DDDFCFB8BE0A43BCA52E743373DBDC03102190@orsmsx416.amr.corp.intel.com> <45DF4CBA.1010906@elischer.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-smp@freebsd.org, Robert Watson , atmblr@gmail.com, "Kunze, Aaron" Subject: Re: Setting CPU affinity to process( Freebsd smp kernel) X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Feb 2007 21:18:36 -0000 On Fri, 23 Feb 2007, Julian Elischer wrote: > Kunze, Aaron wrote: >> Thanks for the info. The Linux equivalent would be sched_setaffinity >> which takes a bitmask as input, allowing the user to define which >> processors will run a particular thread. Here's a link: >> >> http://ibm5.ma.utexas.edu/cgi-bin/man-cgi?sched_setaffinity+2 >> >>>> There's a potential for conflict between the kernel's use of pinning and >>>> binding for kernel synchronization and the user space affinity model, >>>> which will be >> >> Can you elaborate on this? Some of my colleagues and I are considering >> tackling this and would like to avoid such pitfalls, if possible. > > [...] > >>> >>> I know Solaris has processor_bind(2) and pset_bind(2): >>> >>> http://docs.sun.com/app/docs/doc/816-5167/6mbb2jaeu?a=expand#P > > I prefer the linux model but it does limit you to some set number of > procesors. > it looks however that the solaris interface doesn't allow 'sets' of > processors but > just allows you to specify a single processor. Why do you say that? Solaris has pset_bind(2) as well as other pset_foo(). -- DE