From owner-freebsd-hackers Wed Feb 6 18: 4:14 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id 2D9C737B404 for ; Wed, 6 Feb 2002 18:04:10 -0800 (PST) Received: from pool0137.cvx22-bradley.dialup.earthlink.net ([209.179.198.137] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Ydux-0006g5-00; Wed, 06 Feb 2002 18:04:07 -0800 Message-ID: <3C61E092.5E5A7B45@mindspring.com> Date: Wed, 06 Feb 2002 18:04:02 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Charles Peterman Cc: freebsd-hackers@freebsd.org Subject: Re: Binding a Process to a specific CPU References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG What you are asking for is called "process group negaffinity"; a cheesy way to achieve this is to lock processes to a particular processor instead (forced affinity), which will make sure they don't run on the same processor. THis is a cheesy way of doing it because with two processes on a four CPU system, you won't necessarily get the least loaded CPU. To get forced affinity rather than true negaffinity, use Alfred Perlsteins scheduler patches, or make your own. -- Terry Charles Peterman wrote: > > I am currently playing with a dual CPU machine. > With 4.5, is there a way to guarantee that > two specific processes never end up on the same > processor? > > Or does this question betray my fundamental > ignorance of how processes are allocated on an > SMP based machine? > > Thanks much, > > Charles Peterman > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message