From owner-freebsd-questions@FreeBSD.ORG Wed Aug 30 21:31:08 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4221116A4DE for ; Wed, 30 Aug 2006 21:31:08 +0000 (UTC) (envelope-from skylar@cs.earlham.edu) Received: from quark.cs.earlham.edu (cs.earlham.edu [159.28.230.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id E439D43D60 for ; Wed, 30 Aug 2006 21:31:02 +0000 (GMT) (envelope-from skylar@cs.earlham.edu) Received: from [128.95.231.218] (angband.gs.washington.edu [128.95.231.218]) (authenticated bits=0) by quark.cs.earlham.edu (8.13.6/8.13.3) with ESMTP id k7ULUnqR063878 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Aug 2006 17:30:54 -0400 (EDT) (envelope-from skylar@cs.earlham.edu) X-Authentication-Warning: quark.cs.earlham.edu: Host angband.gs.washington.edu [128.95.231.218] claimed to be [128.95.231.218] Message-ID: <44F6036E.7050203@cs.earlham.edu> Date: Wed, 30 Aug 2006 14:30:22 -0700 From: Skylar Thompson Organization: Earlham College Computer Science Department User-Agent: Mail/News 1.5.0.5 (X11/20060728) MIME-Version: 1.0 To: Jordi Carrillo References: <94ff3700608301020l34251166nbdb4d72842e1bb86@mail.gmail.com> <20060830181240.65785.qmail@web83106.mail.mud.yahoo.com> <94ff3700608301302n13f9aabcs935fbe6403601d30@mail.gmail.com> In-Reply-To: <94ff3700608301302n13f9aabcs935fbe6403601d30@mail.gmail.com> X-Enigmail-Version: 0.94.0.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig1D4B9E908A40999963E99FB3" X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (quark.cs.earlham.edu [159.28.230.3]); Wed, 30 Aug 2006 17:30:55 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.2/1623/Wed Jul 26 18:35:11 2006 on quark.cs.earlham.edu X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.56 on 159.28.230.3 X-Spam-Status: No, score=-2.5 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on quark.cs.earlham.edu Cc: backyard1454-bsd@yahoo.com, freebsd-questions@freebsd.org Subject: Re: SMP detection X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: skylar@cs.earlham.edu List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2006 21:31:08 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1D4B9E908A40999963E99FB3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Jordi Carrillo wrote: > 2006/8/30, backyard : >> >> >> >> --- Jordi Carrillo wrote: >> >> > I've read that SMP should be disabled for >> > performance issues (I did not know >> > that before installing freebsd). I have a P4 3GHz >> > with hyperthreading >> > technology. I have the SMP-GENERIC kernel and it >> > only launches one cpu. So, >> > I've decided to disable SMP from BIOS. Is that ok?, >> > knowing that I have a >> > Smp enabled kernel? or should I install one without >> > smp? If so, is there a >> > way to install one already precompiled? >> > Thanks in advance >> > >> > -- >> > http://jordilin.wordpress.com >> > _______________________________________________ >> > freebsd-questions@freebsd.org mailing list >> > >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> > To unsubscribe, send any mail to >> > "freebsd-questions-unsubscribe@freebsd.org" >> > >> >> if the system runs with one cpu now and you don't >> enable smp with HT with the sysctl variable then you >> should be ok. If your not doing SMP then recompiling >> the kernel for single processor mode will make things >> run a little quicker because the SMP code won't come >> into play. >> >> with HT disabling in FreeBSD is more for the security >> issues about a potential exploit whereby one process >> in one pipe can access the priveledged information of >> a process in another pipe because the two cores share >> one processor cache and thus one cache table. To my >> knowledge this hasn't been exploited yet. >> >> If you just install the generic kernel you it should >> be only the uniprocessor one. I would just do a: >> >> cd /usr/src && make buildworld && make >> KERNCONF=3DGENERIC buildkernel && make KERNCONF=3DGENERIC >> installkernel >> >> as opposed to a binary version assuming you haven't >> updated yet you won't have to install world but I >> believe it must have the build in the source tree to >> build a kernel. On your P4 though the difference >> between SMP and uniproc may not be worth the trouble >> because I don't think much of a gain would be made. on >> a P1 a much different story... >> >> if you aren't concerned with bad users or hackers >> hitting the box I would just enable HT with the sysctl >> variable. This will not make things run slower at all, >> just (in theory) less secure, which is why the >> veriable was created in the first place as I recall. >> If you are concerned I would wait until you update >> your system and then just build a GENERIC/CUSTOM >> kernel without the SMP option set. >> >> >> -brian >> > > > I will disable smp from bios. If I have a smp kernel, I suppose there > will > be no problem after all. Would that be ok? > The problem with having SMP enabled is that the smp kernel only > detects one > cpu and the system monitor only features one cpu as well as gkrellm (in= > Linux it shows two cpus). When compiling the system monitor shows the > cpu at > a maximum of 50%, so what's going on with the other 50%? > writing machdep.hlt_logical_cpus to 2 in loader.conf does not solve > anything. I believe FreeBSD uses the other logical CPU to handle hardware interrupts, which can still help performance. You can check dmesg to see how it's actually handling it. --=20 -- Skylar Thompson (skylar@cs.earlham.edu) -- http://www.cs.earlham.edu/~skylar/ --------------enig1D4B9E908A40999963E99FB3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (SunOS) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE9gNxsc4yyULgN4YRAhafAJ90lPqRE9dmZN89n2JFOtCLh06yVwCfdIOC 8fw31hwZW4j5jA/JLadgAhI= =vaZC -----END PGP SIGNATURE----- --------------enig1D4B9E908A40999963E99FB3--