1 Apr 2010 09:16
Re: Two SpeedStep issues
Michael van Elst <mlelstv <at> serpens.de>
2010-04-01 07:16:22 GMT
2010-04-01 07:16:22 GMT
denbrok <at> uni-bonn.de writes: >One is equipped with a Core2Duo E8200. NetBSD reports 800 700 600 >as the frequencies available. I think this should be 2666, 2333 >and 2000 or similar. I don't know whether this makes a practical >difference, but it irritates me a little. That's probably correct. The speedstep frequency parameter is scaled by the bus clock and it is likely that the driver does not identify this correctly. If you build the kernel with options EST_DEBUG you will get some information about the data found. However, this shouldn't affect how EST works. Configuring 800, 700 or 600 should result in real clock values of 2666, 2333 and 2000 respectively. >The other one, a ThinkPad R50e, is equipped with a Celeron M 1400. >I didn't really expect it to have SpeedStep support at all, but >OpenBSD (in practice) claims to lower its frequency to as low as >367 MHz, claiming the battery would then last about 6 hours. Celeron M was used for many different CPUs. What does the kernel (or cpuctl identify) say? Enhanced SpeedStep is signaled with the EST flag in the features2 register. If the there is the EST flag but the est driver doesn't recognize SpeedStep then it is because the CPU reports minimum and maximum clocks to be the same. This is Intels way to say: don't play with it but use the(Continue reading)
This is how I start nfsd:
nfs_server=YES nfsd_flags="-t -u -n 16"
I can see only one nfsd process (maybe this is normal; under NetBSD 4.0
I saw 16 processes (or threads)) in top or ps.
The nfs server is a domU with 2048 MB of RAM and the disks are mounted
with softdeps (not brave enough to try out log).
Maybe I can find the courage to try
log with the 4.7 TB partition I have. I'm just afraid of problems with
partitions as large as this.
> Just as a data point, I'm using 5.99.24 -current on my quad-core amd64
> nfs server with no issues. I'm serving two file systems (one each on
> two separate drives) with occassional heavy access (one is my NetBSD
> source tree, the other holds my $TOOLDIR, $OBJDIR, and other "outputs"
> from build.sh). And both fole systems are mounted with "-o log".
>
> No issues to report, and performance is really pretty good across my 1GB
> Ethernet backbone.
I "upgraded" my 4.0 server to netbsd-5 by extracting the tarballs over
the old binaries, so old libraries and stuff were not deleted. Maybe this
is causing me problems.. is it possible that the new nfsd is using libs
from NetBSD 4.0 and this is causing problems?
RSS Feed