From owner-freebsd-hackers Mon Jun 26 9:43:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sharmas.dhs.org (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id 5CA7C37BA40 for ; Mon, 26 Jun 2000 09:43:33 -0700 (PDT) (envelope-from adsharma@sharmas.dhs.org) Received: (from adsharma@localhost) by sharmas.dhs.org (8.9.3/8.9.3) id JAA07293; Mon, 26 Jun 2000 09:42:46 -0700 Date: Mon, 26 Jun 2000 09:42:46 -0700 From: Arun Sharma To: freebsd-hackers@freebsd.org Message-Id: Posted-To: mpc.lists.freebsd.hackers,muc.lists.freebsd.hackers Subject: Re: VM coloring description in NOTES References: <59063B5B4D98D311BC0D0001FA7E4522026D76AF@l04.research.kpn.com> Reply-To: adsharma@sharmas.dhs.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [This message has also been posted.] On Mon, 26 Jun 2000 10:42:35 +0100, Koster, K.J. wrote: > > > > > > currently -> candidate > > > > PQ_HUGECACHE PQ_CACHE1024 > > > > PQ_LARGECACHE PQ_CACHE512 > > > > PQ_MEDIUMCACHE PQ_CACHE256 > > > > PQ_NORMALCACHE PQ_CACHE64 > > > Hmm. At boot time, the BIOS displayes this square box with a lot of grub in > it that FreeBSD then proceeds to rediscover. Is there no way to whack the > BIOS into submission and have it cough up the cache size? > > It's probably going to be BIOS-vendor specific *sigh*. Then again, perhaps > it would be nice to have an interface to some of the more widely used > bioses. I image you could pry all sorts of tuning information about the > machine from its clammy little hands. Cache size, cache scheme, memory type. 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 ? -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message