From owner-freebsd-stable@FreeBSD.ORG Thu Sep 16 22:19:59 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A593B16A4CE for ; Thu, 16 Sep 2004 22:19:59 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 953F243D2D for ; Thu, 16 Sep 2004 22:19:59 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 618C97A3D2; Thu, 16 Sep 2004 15:19:59 -0700 (PDT) Message-ID: <414A118F.6050007@elischer.org> Date: Thu, 16 Sep 2004 15:19:59 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Stephen Montgomery-Smith References: <4143931B.5080104@math.missouri.edu> In-Reply-To: <4143931B.5080104@math.missouri.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@FreeBSD.org Subject: Re: 2 Processors under FreeBSD 5.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Sep 2004 22:19:59 -0000 Stephen Montgomery-Smith wrote: > I have a dual Athlon MP computer, and I have a very recent version of > FreeBSD 5.3 running on it. > > If I start 6 computer intensive processes, and then kill 3 of them > that are using (say) processor 1, > then the other 3 processes are all processor 0, and as such only get > 33% computer time each. > > Under FreeBSD 4.10 they would have got 66% computer time each, because > there each process didn't seem stuck to a particular processor. > > Is there a sysctl variable that controls this, or is this a bug in > FreeBSD 5.3, or what is going on? > > Here is the computer intensive process: > > main() { > int i; > while(1) {i++;} > } what scheduler are you using?