From owner-freebsd-current Sun Jan 17 14:33:34 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11261 for freebsd-current-outgoing; Sun, 17 Jan 1999 14:33:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell7.ba.best.com (shell7.ba.best.com [206.184.139.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11256 for ; Sun, 17 Jan 1999 14:33:33 -0800 (PST) (envelope-from spadger@shell7.ba.best.com) Received: (from spadger@localhost) by shell7.ba.best.com (8.9.2/8.9.2/best.sh) id OAA14740; Sun, 17 Jan 1999 14:32:12 -0800 (PST) From: Andrew Sparrow Message-Id: <199901172232.OAA14740@shell7.ba.best.com> Subject: RE: FreeBSD Celeron and Celeron ( Mendocino ) kernel patch. To: paul@originative.co.uk Date: Sun, 17 Jan 1999 14:32:11 -0800 (PST) Cc: wollman@khavrinen.lcs.mit.edu, culverk@wam.umd.edu, phiber@udel.edu, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I disagree. From an user perspective I think it will be confusing to > general users to report PII when they think they've got a Celeron. From > a support perspective it might be useful to know what CPU is actually > installed rather than just the class of CPU. FWIW, that would be my preference too. It's a warm fuzzy to know that the hardware was correctly identified, even if there's no specific optimisations for it. :) > On a related note, I'd be interested in benchmarks for the Celerons, how > does the on-chip cache compare to the off-chip cache. Very well, it seems. http://www.tomshardware.com has a bunch of benchmarks for the Celerons, both overclocked (overbussed) and regular speed(s), comparisons to AMD K6's and PIIs, as well as much interesting information on motherboards, chipsets and CPUs - including why the Slot 1 form factor is already doomed.. Cheers, AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message