On Tue, Jan 19, 2016 at 06:44:11PM +0200, Moni Shoua wrote:
On Sat, Jan 9, 2016 at 4:59 PM, Dennis Dalessandro <dennis.dalessandro@xxxxxxxxx> wrote:This series continues adding support for verbs into rdmavt. This brings in completion queue, queue pair, and post send/recv functionality. It also introduces event tracing and moves some more of the hfi1/qib registration functionality. This patch set applies on top of the "Start to rely on rdmavt for qp support" series previously submitted. --- Dennis Dalessandro (8): IB/rdmavt: Add completion queue functions IB/rdmavt: Add post send to rdmavt IB/rdmavt: Add support for tracing events IB/rdmavt: Add modify qp IB/rdmavt: Add destroy qp verb IB/rdmavt: Add post receive to rdmavt IB/rdmavt: Add multicast functions IB/rdmavt: Add misc dev register functionalityI didn't see anywhere an API for RVT that handles received packets Did I miss it? If not, what is expected from the lower driver to do when a packet is received?
Similar to my response for the send side, this is the first step. When a packet is received it is handled by the driver. As to the details of just what moves into rdmavt and what stays in the driver is a matter of debate, and a decision which will have to take into account performance aspects. A perfect design from a software engineering standpoint may not always be possible, these are high performance devices and we can't sacrifice that performance.
At any rate, I'd like to focus on the send side next with the recv to follow.
-Denny -- 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
