From: Roland Dreier <rdreier@cisco.com>
To: openib-general@openib.org, linux-kernel@vger.kernel.org
Subject: InfiniBand 2.6.17 merge plans
Date: Mon, 27 Mar 2006 11:56:13 -0800 [thread overview]
Message-ID: <ada7j6f8xwi.fsf@cisco.com> (raw)
As we enter the second week of the 2.6.17 merge window, I thought it
might be helpful to give an update on what I'm thinking about the
remaining pending pieces. This is really to stimulate discussion --
if there's something that you think really should (or shouldn't) be
merged, let me know.
Of course bug fixes are always welcome and can be merged pretty much
any time -- that's the whole point of the stabilization period after
the merge window.
* PathScale ipath driver. In my git tree at
git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband.git ipath
There is still ia64 build breakage and a lot of sparse endian
annotations to clean up before it's mergeable. Also, there are two
issues I still see:
- Working around the IB midlayer SMA (subnet management agent) /
implementation with a character device when ib_mad isn't loaded.
Maybe I'm off-base here objecting to this. Hal and Sean, as the
ib_mad guys, I'd be especially interested in your opinion of this.
- The driver depends on 64BIT && PCI_MSI, and is basically
x86_64-only for practical purposes. I think this is OK as far as
a merge goes, but it would be nice to be able to use a PCIe
device on any system with PCIe slots...
* RDMA CM. In my git tree at
git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband.git rdma_cm
I think this is OK to merge, but I don't see much pull to get it in
right now. There are three consumers on the horizon:
- userspace RDMA CM, which exports the abstraction to userspace.
The feeling is that this interface needs more time to mature.
- NFS/RDMA. Not ready to merge right now.
- iSER. Maybe ready to merge -- I haven't heard anything recently.
My feeling is that without someone making a case for why this
should go in now, I'm going to hold off.
* IPoIB tunables. This is probably OK but I haven't seen any patches
yet, so we're running out time.
* SRP FMRs. I have a patch that I'm pretty happy with now, so I
think this will go in. This will need a lot of testing, or we may
have to turn it off by default for 2.6.17 final
So if you care about any of this, let me know what you think. And if
there's something not on this list and not in
git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband.git for-2.6.17
please make sure I know about it, or it won't get merged.
Thanks,
Roland
next reply other threads:[~2006-03-27 19:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 19:56 Roland Dreier [this message]
2006-03-27 20:19 ` [openib-general] InfiniBand 2.6.17 merge plans Sean Hefty
2006-03-27 20:24 ` Roland Dreier
2006-03-27 22:58 ` Roland Dreier
2006-03-27 23:42 ` Sean Hefty
2006-03-27 23:51 ` Roland Dreier
2006-03-27 23:53 ` Sean Hefty
2006-03-28 18:47 ` Bob Woodruff
2006-03-29 8:28 ` Dan Bar Dov
2006-03-29 17:03 ` Roland Dreier
2006-04-03 10:31 ` Dan Bar Dov
2006-04-03 15:46 ` Roland Dreier
2006-03-29 23:30 ` Bryan O'Sullivan
2006-03-30 22:51 ` updated " Roland Dreier
2006-03-30 23:11 ` [openib-general] " Roland Dreier
2006-03-31 6:32 ` Christoph Hellwig
2006-03-31 16:36 ` Roland Dreier
2006-03-30 23:18 ` Sean Hefty
2006-04-02 6:58 ` Michael S. Tsirkin
2006-04-02 22:36 ` Roland Dreier
2006-04-03 22:02 ` Michael S. Tsirkin
2006-04-03 22:04 ` Roland Dreier
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=ada7j6f8xwi.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openib-general@openib.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.