On May 14, 2008, at 10:52 AM, Ben Gardiner wrote:
So there likely are reasons why the following is not possible:
That's way too much code for a tlb exception handler.
From a system resource perspective, you are much better
off with a small and efficient piece of tlb loading code,
always invalidating pages on both ends and taking the
tlb exception fault. Unfortunately, this could cause some
thrashing edge cases, so a little intelligence would be
needed. Exception processing isn't free, and it quickly
destroys the cache footprint of your application, further
slowing down the entire system. The tlb reload handler
goal should be maximum of 8 instructions and 4 memory
accesses, not 4K of elaborate conditional testing. :-)
Thanks.
-- Dan
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
