Ralf Baechle <ralf@xxxxxxxxxxxxxx> writes: > 16K is a silver bullet solution to all cache aliasing problems. So if > your issue persists with 16K page size, it's not a cache aliasing issue. > Aside there are generally performance gains from the bigger page size. I wonder why isn't the issue present in other cases. Perhaps remapping of a userspace address and accessing it with kseg0 isn't a frequent operation. Shouldn't we change the default page size (on affected CPUs) to 16 KB then? Alternatively, we could flush/invalidate the cache when needed - is it a viable option? Thanks. -- Krzysztof Halasa Research Institute for Automation and Measurements PIAP Al. Jerozolimskie 202, 02-486 Warsaw, Poland
