From owner-freebsd-current@FreeBSD.ORG Sat Aug 23 18:18:55 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8992816A4BF for ; Sat, 23 Aug 2003 18:18:55 -0700 (PDT) Received: from mx1.trigger.net (ns1.trigger.net [199.166.206.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9DC043FBD for ; Sat, 23 Aug 2003 18:18:54 -0700 (PDT) (envelope-from mikej@trigger.net) Received: from localhost (localhost [127.0.0.1]) by mx1.trigger.net (Postfix) with ESMTP id 6BE9B1238F2; Sat, 23 Aug 2003 21:18:50 -0400 (EDT) Received: from mx2.trigger.net (unixweb.trigger.net [199.166.206.9]) by mx1.trigger.net (Postfix) with ESMTP id 9C4B61238F4; Sat, 23 Aug 2003 21:18:49 -0400 (EDT) Received: by mx2.trigger.net (Postfix, from userid 80) id ECAE6625025; Sat, 23 Aug 2003 21:18:53 -0400 (EDT) Received: from 63.139.119.223 (SquirrelMail authenticated user mikej) by webmail.trigger.net with HTTP; Sat, 23 Aug 2003 21:18:53 -0400 (EDT) Message-ID: <2092.63.139.119.223.1061687933.squirrel@webmail.trigger.net> In-Reply-To: <20030823022938.GA128@rot13.obsecurity.org> References: <20030822230857.GA99046@rot13.obsecurity.org><1764.63.139.119.223.1061605432.squirrel@webmail.trigger.net> <20030823022938.GA128@rot13.obsecurity.org> Date: Sat, 23 Aug 2003 21:18:53 -0400 (EDT) From: mikej@trigger.net To: "Kris Kennaway" User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-Virus-Scanned: by AMaViS cc: current@freebsd.org Subject: Re: HTT on current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Aug 2003 01:18:55 -0000 > On Fri, Aug 22, 2003 at 10:23:52PM -0400, mikej@trigger.net wrote: > >> Well i've enabled all SMP options, recompiled and rebooted. The CPUs now >> properly show up in dmesg and i can see the C header in top. However no >> processes seem to be being assigned to cpu 1. Why is the schedueler only >> using CPU 0? This wasnt the behaviour in stable. > > Which scheduler? Please try to be as explicit as you can when sending > bug reports. > > Kris > The default BSD schedueler. All processes seem to be on CPU0 according to top. options SCHED_4BSD #4BSD scheduler