Re: Duron kernel crash (i686 works)

Alan Cox (
Wed, 12 Sep 2001 13:48:20 +0100 (BST)

> So why it is oopses then?

On correct hardware it doesnt seem to oops.

> Also, we don't want this data to arrive late or whatever.
> fast_copy_page must copy page (make it so that memcpy()==0).
> If it does not, it is too much "optimized".

See the "sfence" instruction

> A better way to do it is to bencmark several routines at
> startup time and pick the best one. It is done now
> for RAID xor'ing routine.

Not in this case. It is Athlon specific code. It was fine tuned when it
was written
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at