Just curious because I have no experience in this area... but what exactly
does cache coloring get us... I've never actually gotten a really straight
answer on this... Thanks
=================================================================
| Kenneth Culver | FreeBSD: The best NT upgrade |
| Unix Systems Administrator | ICQ #: 24767726 |
| and student at The | AIM: muythaibxr |
| The University of Maryland, | Website: (Under Construction) |
| College Park. | http://www.wam.umd.edu/~culverk/|
=================================================================
On Mon, 26 Jun 2000, Arun Sharma wrote:
> [This message has also been posted.]
> On Mon, 26 Jun 2000 10:42:35 +0100, Koster, K.J. <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
