From owner-freebsd-questions@FreeBSD.ORG Mon May 26 18:19:30 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7F28106566B for ; Mon, 26 May 2008 18:19:30 +0000 (UTC) (envelope-from jos@webrz.net) Received: from webrz.xs4all.nl (webrz.xs4all.nl [82.95.248.216]) by mx1.freebsd.org (Postfix) with ESMTP id 3FD688FC17 for ; Mon, 26 May 2008 18:19:30 +0000 (UTC) (envelope-from jos@webrz.net) Received: from webrz.xs4all.nl (localhost.webrz.net [127.0.0.1]) by webrz.xs4all.nl (Postfix) with ESMTP id 683E7FD06A for ; Mon, 26 May 2008 20:20:07 +0200 (CEST) Received: from [10.10.10.27] (atlantis.webrz.net [10.10.10.27]) by webrz.xs4all.nl (Postfix) with ESMTP id 44117FD061 for ; Mon, 26 May 2008 20:20:07 +0200 (CEST) Message-ID: <483AFF30.2090108@webrz.net> Date: Mon, 26 May 2008 20:19:28 +0200 From: Jos Chrispijn User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <483ADEA1.40206@webrz.net> <483AE57B.2000106@magichamster.com> <483AEB21.4070100@webrz.net> <483AF28F.1080102@magichamster.com> In-Reply-To: <483AF28F.1080102@magichamster.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AV-Checked: ClamAV using ClamSMTP @ prometheus.webrz.net Subject: Re: Kernel for Dual Core X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 May 2008 18:19:30 -0000 Mark, Mark Ovens wrote: > The reason that nothing is #'d out and just about everything is in > GENERIC is because it is exactly that, a *generic* kernel, and soo > needs to be able to boot on any hardware it's installed on. Oke, now I understand. > The advantage of building a custom kernel is that you remove anything > your system doesn't have which saves time when booting as the kernel > won't be probing for devices that it will never find - for example. > mine is an all-SCSI system so my kernel doesn't have any IDE or floppy > devices in it - and it makes the kernel smaller (although that isn't > really an issue these days). With this speed that shouldn't be a problem... > An alternative is to go into the configuration editor from the main > boot menu and disable those compiled-in devices that you don't have. That I didn't know! > To confirm that your running kernel has detected and started both CPUs: > > /home/mark{8}% grep -i cpu /var/log/messages > > May 26 12:10:30 redshift kernel: CPU: AMD Athlon(TM) MP 2800+ > (2133.42-MHz 686-class CPU) > May 26 12:10:30 redshift kernel: FreeBSD/SMP: Multiprocessor System > Detected: 2 CPUs > May 26 12:10:30 redshift kernel: cpu0 (BSP): APIC ID: 0 > May 26 12:10:30 redshift kernel: cpu1 (AP): APIC ID: 1 > May 26 12:10:30 redshift kernel: cpu0: on acpi0 > May 26 12:10:30 redshift kernel: cpu1: on acpi0 > May 26 12:10:30 redshift kernel: SMP: AP CPU #1 Launched! > /home/mark{9}% I did this on my systems on which I installed FreeBSD from iso CD's: May 25 17:23:44 triton kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs May 25 17:23:44 triton kernel: cpu0 (BSP): APIC ID: 0 May 25 17:23:44 triton kernel: cpu1 (AP): APIC ID: 1 May 25 17:23:44 triton kernel: cpu0: on acpi0 May 25 17:23:44 triton kernel: est0: on cpu0 May 25 17:23:44 triton kernel: p4tcc0: on cpu0 May 25 17:23:44 triton kernel: cpu1: on acpi0 May 25 17:23:44 triton kernel: est1: on cpu1 May 25 17:23:44 triton kernel: p4tcc1: on cpu1 May 25 17:23:44 triton kernel: SMP: AP CPU #1 Launched! So this would mean that I allready use a dual core tuned system? When should it say SMP: AP CPU #2 Launched! ? Thanks for sharing, Jos