From: "Woodruff, Robert J" <woody@co.intel.com>
To: "Linus Torvalds" <torvalds@osdl.org>,
"Sam Ravnborg" <sam@ravnborg.org>, "Greg KH" <greg@kroah.com>
Cc: "Timothy Miller" <miller@techsource.com>,
"Rik van Riel" <riel@redhat.com>,
"Matti Aarnio" <matti.aarnio@zmailer.org>,
"Christoph Hellwig" <hch@infradead.org>,
"Woodruff, Robert J" <woody@jf.intel.com>,
<linux-kernel@vger.kernel.org>,
"Hefty, Sean" <sean.hefty@intel.com>,
"Coffman, Jerrie L" <jerrie.l.coffman@intel.com>,
"Davis, Arlin R" <arlin.r.davis@intel.com>,
<marcelo.tosatti@cyclades.com>
Subject: RE: PATCH - InfiniBand Access Layer (IBAL)
Date: Sat, 13 Mar 2004 14:07:13 -0800 [thread overview]
Message-ID: <1AC79F16F5C5284499BB9591B33D6F000B6306@orsmsx408.jf.intel.com> (raw)
On Wed, 25 Feb 2004, Linus Torvalds wrote:
>Oh, I agree that _reviewing_ code is good, together with feedback
>on what would improve its chances of getting accepted later on.
>But it should be clear that regardless,
>we don't add features that nobody
>can sanely test and where hardware isn't available.
>
> Linus
Just wanted to give an update on where we are with the InfiniBand IBAL.
After we submitted the IBAL code for review, there has been additional
InfiniBand code put into open source by the major InfiniBand companies,
namely TopSpin, Mellanox, InfiniCon, and Voltaire.
This presents somewhat of a problem because now there are multiple
versions of the various InfiniBand S/W components, Access Layers, and
ULPs.
We now need to review all this code and
determine which code is best to use as a basis for something that
we would eventually try to get into Linux. We hope that people in the
linux community will help us sort through this mess and come up with
a "best of breed" stack out of all the available code.
The Mellanox and Topspin folks along with some people from some of
the national labs are trying to start up a website called openib.org,
with data bases, email lists, etc. where people can submit code for
this "best of breed" stack and discuss it. As long as it is truly
open, the linux community is allowed to participate, and the code
is evaluated on it's technical merits, rather than one companies
personal
agenda, this forum might serve as a way for us to sort through this
without
taking every issue to lkml.
What are your thoughts on how we should proceed ?
next reply other threads:[~2004-03-13 22:08 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-13 22:07 Woodruff, Robert J [this message]
2004-03-14 1:13 ` Andrew Morton
2004-03-14 2:28 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2004-03-20 19:15 Acker, Dave
2004-03-20 17:15 Acker, Dave
2004-03-20 17:55 ` Ulrich Drepper
2004-03-21 22:16 ` Roland Dreier
2004-03-15 22:52 Woodruff, Robert J
2004-03-15 23:17 ` Christoph Hellwig
2004-03-15 23:44 ` Johannes Erdfelt
2004-03-15 23:48 ` Christoph Hellwig
2004-03-15 23:54 ` Johannes Erdfelt
2004-03-16 0:09 ` Christoph Hellwig
2004-03-16 0:18 ` Johannes Erdfelt
2004-03-16 1:41 ` Roland Dreier
2004-03-19 18:47 ` Ulrich Drepper
2004-03-19 19:21 ` Fab Tillier
2004-03-19 20:20 ` Ulrich Drepper
2004-03-19 20:47 ` Roland Dreier
2004-03-14 23:14 Nivedita Singhvi
2004-03-14 3:46 Woodruff, Robert J
2004-03-15 2:10 ` Greg KH
2004-02-24 23:02 Woodruff, Robert J
2004-02-25 3:32 ` Rik van Riel
2004-02-24 22:18 Woodruff, Robert J
2004-02-24 21:33 Woodruff, Robert J
2004-02-24 19:29 Woodruff, Robert J
2004-02-24 19:44 ` Greg KH
2004-02-24 19:50 ` Christoph Hellwig
2004-02-24 19:57 ` Greg KH
2004-02-24 22:29 ` Rik van Riel
2004-02-25 0:28 ` Matti Aarnio
2004-02-25 3:39 ` Rik van Riel
2004-02-25 16:25 ` Timothy Miller
2004-02-25 17:34 ` Roland Dreier
2004-02-25 18:55 ` Sam Ravnborg
2004-02-25 18:05 ` Linus Torvalds
2004-02-25 19:09 ` Timothy Miller
2004-02-25 19:55 ` Sam Ravnborg
2004-02-25 19:05 ` Linus Torvalds
2004-02-25 13:19 ` Christoph Hellwig
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=1AC79F16F5C5284499BB9591B33D6F000B6306@orsmsx408.jf.intel.com \
--to=woody@co.intel.com \
--cc=arlin.r.davis@intel.com \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=jerrie.l.coffman@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=matti.aarnio@zmailer.org \
--cc=miller@techsource.com \
--cc=riel@redhat.com \
--cc=sam@ravnborg.org \
--cc=sean.hefty@intel.com \
--cc=torvalds@osdl.org \
--cc=woody@jf.intel.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
all inboxes | Powered by JetHome®