> Yeah, but that means the completion has to be delivered from process > context. That's not what aio does today, and it'd be a real performance > regression. It'd only have to to complete from process context if it faults. The cheapest possible delivery mechanism is simple cpu stores. In the vast majority of cases the ring will be resident and it'll be done. In rare cases it could fall back to a deferred completion. If apps can't stomach that latency and want to pay the overhead of pinning to remove that risk, they're welcome to do so. That's my hope, anyway. - z -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
