From: Sean Hefty <mshefty@ichips.intel.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: openib-general@openib.org, linux-kernel@vger.kernel.org
Subject: Re: [openib-general] updated InfiniBand 2.6.17 merge plans
Date: Thu, 30 Mar 2006 15:18:02 -0800 [thread overview]
Message-ID: <442C672A.2030707@ichips.intel.com> (raw)
In-Reply-To: <ada1wwj1r7r.fsf@cisco.com>
Roland Dreier wrote:
> * RDMA CM. In my git tree at
>
> git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband.git rdma_cm
>
> None of the users of this code look are to merge, and it looks like
> there's some changes in the design happening now. Seems like this
> can and should wait for 2.6.18.
Does it make sense to merge the first two patches of that patch series?
1. Provide common handling for marshalling data between userspace clients and
kernel mode Infiniband drivers.
2. Extend the Infiniband CM to include private data comparisons as part of its
connection request matching process.
This would make it easier to keep the openib tree in sync with the kernel.
- Sean
next prev parent reply other threads:[~2006-03-30 23:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 19:56 InfiniBand 2.6.17 merge plans Roland Dreier
2006-03-27 20:19 ` [openib-general] " 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 [this message]
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=442C672A.2030707@ichips.intel.com \
--to=mshefty@ichips.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=rdreier@cisco.com \
/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).