On Mon, 17 Mar 2003, Jason R Thorpe wrote:

> On Mon, Mar 17, 2003 at 02:13:22PM +0100, Johnny Billquist wrote:
> 
>  > The reason is that agressive caching means that the CPU will be doing a
>  > lot of memory to memory copying, instead of using the controller DMA. On a
> 
> And how do you figure that?

Like I said, I haven't really checked anything up, it's just some
semi-unqualified guessing.

Since you probably know for sure, you might as well settle this once and
for all. Is the file caching totally zero-copy stuff?

If so, do you have any other good ideas why I see peaks of over 70% system
time when running build.sh. (And this is not when running gcc).

	Johnny

Johnny Billquist                  || "I'm on a bus
                                  ||  on a psychedelic trip
email: bqt@update.uu.se           ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol