> cpu_relax();
> + barrier();
Gah, now I look over the source I see that cpu_relax() is always
used together with barrier() ...
I guess the best long-term thing (2.5) would be to build a barrier
into cpu_relax(), but for 2.4-rmap I'll just add your patch.
-
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/