On Sun, Feb 02, 2014 at 07:21:04PM +0000, Al Viro wrote: > BTW, is there any reason why fuse/dev.c doesn't use atomic kmaps for > everything? After all, as soon as we'd done kmap() in there, we > grab a spinlock and don't drop it until just before kunmap(). With > nothing by memcpy() done in between... Miklos? AFAICS, we only win s/by/but/ - sorry... > from switching to kmap_atomic there - we can't block anyway, we don't > need it to be visible on other CPUs and nesting isn't a problem. > Looks like it'll be cheaper in highmem cases and do exactly the same > thing as now for non-highmem... Comments? > -- > To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
