> cause any CPU load (or more precisely, non-measurable load). However, with
> mach64 and r128, it DOES. I did some more research.
Makes sense
> memcpy-ing 380kB at 25fps takes about 5ms per frame and causes X to eat 1% cpu
> time (time measurements were done by tsc)
> memcpy-ing 760kB at 25fps takes about 11ms per frame, but instead of eating
> 2% CPU time, it eats 35% (yes, that's 35 times more)
So presumably at this bandwidth you are beginning collide with the graphics
controllers and it will stall your cycles, at which point its going to stall
the CPU so effectively eat CPU time
Sounds like a reasonable explanation to me
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Aug 31 2001 - 21:00:24 EST