Re: [lkml]Re: Matrox FB console driver

[thunder7@xs4all.nl]

On Tue, Apr 24, 2001 at 06:19:31AM -0500, Andy Carlson wrote:
> time prime before x
> real    1m23.535s
> user    0m40.550s
> sys     0m42.980s
> 
> /proc/mtrr before x
> reg00: base=0x00000000 (   0MB), size= 256MB: write-back, count=1
> reg01: base=0xfd800000 (4056MB), size=   4MB: write-combining, count=1
> 
> time prime after x
> real    0m48.732s
> user    0m41.070s
> sys     0m7.690s
> 
> /proc/mtrr after x
> reg00: base=0x00000000 (   0MB), size= 256MB: write-back, count=1
> reg01: base=0xfd800000 (4056MB), size=   4MB: write-combining, count=1
> 
> time prime in X
> real    0m42.835s
> user    0m41.180s
> sys     0m1.710s
> 
Well, it isn't that.
Still, it was recently discussed that X might leave some settings in the
video-card (Matrox).

So I tried the following:

time spdtest.sh before X with spdtest.sh:

#!/bin/sh
i=1
while [ $i -lt 500 ]
do
   clear
   echo $i
   cat test.out;
   i=`expr $i + 1`
done

and after X, no change.
This is a G400/32 Mb with framebuffer @ 1600x1200x16bpp, and X 4.0.3,
same resolution. Kernel 2.4.3-ac12, Abit VP6 dual P3/866.

There was no significant change in any of the reported times.

I don't know. Your problem is interesting. Do other programs have this
too?

Jurriaan
-- 
And the gosts of hope walk silent halls
At the death of the promised land
All is gone, all is gone
But these changing winds can turn cold and hostile
	New Model Army
GNU/Linux 2.4.3-ac12 SMP/ReiserFS 2x1743 bogomips load av: 0.00 0.03 0.01