From owner-freebsd-hackers Mon Jun 26 12: 9:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id A46E637BCB4 for ; Mon, 26 Jun 2000 12:09:19 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id PAA21653; Mon, 26 Jun 2000 15:09:10 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id PAA49039; Mon, 26 Jun 2000 15:09:10 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 26 Jun 2000 15:09:10 -0400 (EDT) To: adsharma@sharmas.dhs.org Cc: freebsd-hackers@freebsd.org Subject: Re: VM coloring description in NOTES In-Reply-To: References: <59063B5B4D98D311BC0D0001FA7E4522026D76AF@l04.research.kpn.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14679.40851.766762.577274@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Arun Sharma writes: > > For Intel processors, CPUID instruction spits out both L1 and L2 cache > sizes. Perhaps, these things should be made a runtime option than a > compile time option ? That sounds like a good idea. Also, I imagine that it would be possible to write a function to emperically determine the system cache size on non Intel CPUs where such an instruction is not available. Eg, Alpha processors don't specify the amount of Bcache (secondary or tertiary) cache they have & Tru64 sizes them on the fly. Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message