Hugh> Could anyone please shed light on PREFETCH_STRIDE, and in
Hugh> particular its sole use:
Hugh> prefetchw(pmd+j+(PREFETCH_STRIDE/16)); in mm/memory.c:
Hugh> That looks to me suspiciously like something inserted to suit
Hugh> one particular architecture - ia64? is it really suitable for
Hugh> others? is 4*L1_CACHE_SIZE really right for PREFETCH_STRIDE on
Hugh> anything that prefetches except ia64? what's the "/ 16"?
Hugh> shouldn't there be a "/ sizeof(pmd_t)" somewhere (PAE or not)?
Hugh> is it right to prefetch each time around that loop? isn't it
Hugh> appropriate only to the exit_mm (0 to TASK_SIZE) clearance?
Hugh> All in all, I'm thinking that line shouldn't be there, or not
Hugh> without a substantial comment...
That code certainly wasn't optimized for ia64. Furthermore, I also do
not like the prefetch distance it's using. In fact, in my ia64-patch,
I use the following code instead:
prefetchw(pmd + j + PREFETCH_STRIDE/sizeof(*pmd));
This is more sensible (because it really does prefetch by the
PREFETCH_STRIDE distance) and it also happens to run (slightly) faster
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/