On 3-Dec-13, at 7:08 PM, James Bottomley wrote:
On Sun, 2013-12-01 at 22:18 +0100, Helge Deller wrote:
This is now the next try to fix the aio bug in our kmap/kunmap
implementation. It's basically stuff from
I thought the implementation required us to move to coherency
management
in the kmap API?, in which case ...
This is what I've been saying to Helge.
We don't fully understand why we need to flush unconditionally to fix
the aio bug
in kunmap. I can see it for coherency and when different non coherent
caches are
involved (e.g., I & D). Could this be SMP related?
I think if we understand the kunmap case, we will also understand the
kmap case.
At the moment, the fix is just based on testing.
Dave
--
John David Anglin dave.anglin@xxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
