From: Sam Ravnborg <sam@ravnborg.org>
To: Timothy Miller <miller@techsource.com>
Cc: Rik van Riel <riel@redhat.com>,
Matti Aarnio <matti.aarnio@zmailer.org>, Greg KH <greg@kroah.com>,
Christoph Hellwig <hch@infradead.org>,
"Woodruff, Robert J" <woody@co.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, torvalds@osdl.org
Subject: Re: PATCH - InfiniBand Access Layer (IBAL)
Date: Wed, 25 Feb 2004 19:55:53 +0100 [thread overview]
Message-ID: <20040225185553.GA2474@mars.ravnborg.org> (raw)
In-Reply-To: <403CCC77.6030405@techsource.com>
> >
> >I'm sure infinibad will be inetresting once htere are
> >actual hardware driver.s However, I'm not aware of any
> >open source drivers in existnace now, so what good is
> >a stack ?
> >
>
> Chicken and egg. If infiniband has some significant value, it would be
> in everyone's favor if we took the initiative.
If we take the vendor persåective here. Then why should they make their
driver open source, when the middle layer is not part of the
main stream kernel?
So short-term I beleive the
"no open source drivers => no interest in IBAL"
is a bit to fast a conclusion.
Let's anyway see what they have, and give them feedback.
Based on the comments I have seen so far there is
a good chance to see open source drivers before IBAL is
considered ready for main stream kernel.
Sam
next prev parent reply other threads:[~2004-02-25 17:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2004-02-24 21:33 Woodruff, Robert J
2004-02-24 22:18 Woodruff, Robert J
2004-02-24 23:02 Woodruff, Robert J
2004-02-25 3:32 ` Rik van Riel
2004-03-13 22:07 Woodruff, Robert J
2004-03-14 1:13 ` Andrew Morton
2004-03-14 2:28 ` Greg KH
2004-03-14 3:46 Woodruff, Robert J
2004-03-15 2:10 ` Greg KH
2004-03-14 23:14 Nivedita Singhvi
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-20 17:15 Acker, Dave
2004-03-20 17:55 ` Ulrich Drepper
2004-03-21 22:16 ` Roland Dreier
2004-03-20 19:15 Acker, Dave
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=20040225185553.GA2474@mars.ravnborg.org \
--to=sam@ravnborg.org \
--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=sean.hefty@intel.com \
--cc=torvalds@osdl.org \
--cc=woody@co.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®