From: Dennis Dalessandro <dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v2 0/8] IB/rdmavt: Add functions for cq, qp, post send and recv
Date: Fri, 22 Jan 2016 13:00:08 -0800 [thread overview]
Message-ID: <20160122205822.7850.25466.stgit@scvm10.sc.intel.com> (raw)
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.
his patch set applies on top of the v2 "Start to rely on rdmavt for qp support"
series previously submitted.
Changes since v1:
Conflict resolution after rebase onto Doug's k.o/for-4.5
---
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 functionality
drivers/infiniband/sw/rdmavt/Makefile | 5
drivers/infiniband/sw/rdmavt/cq.c | 445 +++++++++++++++++++
drivers/infiniband/sw/rdmavt/cq.h | 4
drivers/infiniband/sw/rdmavt/mcast.c | 335 ++++++++++++++-
drivers/infiniband/sw/rdmavt/mcast.h | 2
drivers/infiniband/sw/rdmavt/qp.c | 760 ++++++++++++++++++++++++++++++++-
drivers/infiniband/sw/rdmavt/trace.c | 49 ++
drivers/infiniband/sw/rdmavt/trace.h | 117 +++++
drivers/infiniband/sw/rdmavt/vt.c | 60 +++
include/rdma/rdma_vt.h | 66 +++
include/rdma/rdmavt_cq.h | 99 ++++
include/rdma/rdmavt_mr.h | 9
include/rdma/rdmavt_qp.h | 66 +++
13 files changed, 1974 insertions(+), 43 deletions(-)
create mode 100644 drivers/infiniband/sw/rdmavt/trace.c
create mode 100644 drivers/infiniband/sw/rdmavt/trace.h
create mode 100644 include/rdma/rdmavt_cq.h
--
-Denny
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2016-01-22 21:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 21:00 Dennis Dalessandro [this message]
[not found] ` <20160122205822.7850.25466.stgit-9QXIwq+3FY+1XWohqUldA0EOCMrvLtNR@public.gmane.org>
2016-01-22 21:00 ` [PATCH v2 1/8] IB/rdmavt: Add completion queue functions Dennis Dalessandro
2016-01-22 21:00 ` [PATCH v2 2/8] IB/rdmavt: Add post send to rdmavt Dennis Dalessandro
2016-01-22 21:00 ` [PATCH v2 3/8] IB/rdmavt: Add support for tracing events Dennis Dalessandro
2016-01-22 21:00 ` [PATCH v2 4/8] IB/rdmavt: Add modify qp Dennis Dalessandro
2016-01-22 21:00 ` [PATCH v2 5/8] IB/rdmavt: Add destroy qp verb Dennis Dalessandro
2016-01-22 21:00 ` [PATCH v2 6/8] IB/rdmavt: Add post receive to rdmavt Dennis Dalessandro
2016-01-22 21:00 ` [PATCH v2 7/8] IB/rdmavt: Add multicast functions Dennis Dalessandro
2016-01-22 21:01 ` [PATCH v2 8/8] IB/rdmavt: Add misc dev register functionality Dennis Dalessandro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160122205822.7850.25466.stgit@scvm10.sc.intel.com \
--to=dennis.dalessandro-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).