> That's indeed a good approach. But, we need to have an upper limit > before a batch of events is flushed. Can we decide limit based on > completion event queue size? I think that's fine. We only need to ack before wrapping the 32-bit value, plus ensure that everything is acked when closing the rsocket. But, does this change really make any difference? At the point where ack is called, there's no contention, so the overhead seems small considering that we in a part of the code where we likely just blocked the thread. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
