From: "Woodruff, Robert J" <woody@co.intel.com>
To: "Greg KH" <greg@kroah.com>, "Woodruff, Robert J" <woody@jf.intel.com>
Cc: "Linus Torvalds" <torvalds@osdl.org>,
"Sam Ravnborg" <sam@ravnborg.org>,
"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 19:46:12 -0800 [thread overview]
Message-ID: <1AC79F16F5C5284499BB9591B33D6F000B630B@orsmsx408.jf.intel.com> (raw)
On Sat, Mar 13, 2004 at 02:07:13PM -0800, Greg KH wrote:
>I think you need to work with the openib.org people as they seem to
>have:
> - working code with support for a number of different devices
I have code that has been running MPI NBPs, Pallas benchmark, and IPoIB
stress tests
for almost 10 days now on multiple vendors equipment. We are also close
to having
a major data base vendor's DAPL stress test running very well. I'm
thinkin this code could be
running 1000 nodes clusters within a couple of months, if people wanted
to try it,
but that would require Mellanox to open source their TVPD.
> - developers with extensive kernel programming experience
As if we don't.
> working on cleaning up the code to fit properly into the
> kernel tree.
The comments you have given on IBAL would probably only take a few weeks
to change.
> - their code showing up in at least one distro which will expose
> them to a much wider range of testing than Intel's project so
> far has had.
Ok, the OEMS pushed for and got a distro to accept a TTM solution,
that's OK for getting
InfiniBand jumpstarted,
but does that mean we have to accept it into Linux
and live with that solution forever.
I guess I just wish they had started working with us on this open source
project 2 years ago
when we started it, rather than developing a complete stack behind
closed doors and then
releasing it without any input from anyone. Now there are serious issues
that will take a lot
of work to fix. At least our project was totally open from the
start and anyone could have provided input at any time.
Enough said.
I understand your position. We will submit our code to openib.org.
next reply other threads:[~2004-03-14 3:47 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-14 3:46 Woodruff, Robert J [this message]
2004-03-15 2:10 ` 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-13 22:07 Woodruff, Robert J
2004-03-14 1:13 ` Andrew Morton
2004-03-14 2:28 ` 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=1AC79F16F5C5284499BB9591B33D6F000B630B@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®