From: Dennis Dalessandro <dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org
Cc: gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org,
dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
mike.marciniszyn-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Subject: HFI1 code duplication todo
Date: Thu, 12 Nov 2015 16:13:18 -0500 [thread overview]
Message-ID: <20151112211317.GB11252@phlsvsds.ph.intel.com> (raw)
The major todo for the hfi1 driver in staging is getting rid of the verbs
code duplication between ipath, qib, and now hfi1. The ipath driver has been
deprecated and is going to be deleted soon. So that leaves qib and hfi. To
address this we have proposed rdmavt which will be a common kmod that
provides software RDMA verbs support. qib and hfi1 will both use this as
well as other forthcoming drivers such as soft-roce. See this thread for
some details: http://www.spinics.net/lists/linux-rdma/msg29922.html.
Since that initial RFC we have been accumulating patches in a GitHub repo
for an early look at the development. At some point soon we want to actually
start posting the patches to the mailing list. This is where it gets tricky.
The code basically not only adds a new driver but it modifies two existing
ones, heavily. To make it more murky one driver is in staging the other is
in the usual drivers/infiniband tree.
The question is, how do we go about this logistically due to the 2 drivers
being in separate sub-trees?
Greg, Doug,
As the maintainers of the two trees involved we'd kind of like to get your
thoughts on this.
Thanks
-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:[~2015-11-12 21:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 21:13 Dennis Dalessandro [this message]
[not found] ` <20151112211317.GB11252-W4f6Xiosr+yv7QzWx2u06xL4W9x8LtSr@public.gmane.org>
2015-11-19 22:23 ` HFI1 code duplication todo Dennis Dalessandro
2015-11-20 13:12 ` Dan Carpenter
2015-11-20 15:41 ` Doug Ledford
[not found] ` <564F3F1C.4020508-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-11-20 15:49 ` Marciniszyn, Mike
2015-11-20 16:39 ` Greg KH
[not found] ` <20151120163935.GA10091-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-11-20 16:58 ` Doug Ledford
[not found] ` <564F512A.1060808-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-11-20 17:01 ` Christoph Hellwig
2015-11-20 17:13 ` Greg KH
[not found] ` <20151120171346.GA14829-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-11-20 17:46 ` Doug Ledford
2015-11-20 15:58 ` ira.weiny
2015-11-20 22:25 ` Dan Carpenter
2015-11-21 15:53 ` ira.weiny
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=20151112211317.GB11252@phlsvsds.ph.intel.com \
--to=dennis.dalessandro-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mike.marciniszyn-ral2JQCrhuEAvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.