From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: Greg KH <greg@kroah.com>
Cc: openib-general@openib.org, linux-kernel@vger.kernel.org
Subject: Re: [openib-general] InfiniBand incompatible with the Linux kernel?
Date: Fri, 8 Oct 2004 14:38:06 -0600 (MDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0410081428230.9700@linux.site> (raw)
In-Reply-To: <20041008202247.GA9653@kroah.com>
On Fri, 8 Oct 2004, Greg KH wrote:
> If someone downloads the spec without joining the IBTA, and
> proceeds to use the spec for an implementation of the IBTA spec,
> that person (company) runs the risk of being a target of patent
> infringement claims by IBTA members.
Another solid reason to write infiniband off. I keep hoping that the IB
vendor crowd will stop shooting themselves in the head with such
regularity, and they just won't. They just keep increasing the size of the
bore.
Infiniband can now be spelled a few different ways, "I2O" and "ATM" come
to mind, except that "ATM" was less unsuccessful in its lifetime than IB
has been so far.
> In justification for this position people say that they are just
> trying to get more people to join the IBTA because they need the
> dues, which by coincidence are $9500 per year, and point out
> that some other commonly used specs are similarly made available
> for steep prices. I don't know one way or the other about that
> but this sounds a lot like the reason that we all gave ourselves
> for NOT including SDP in the kernel[1].
> So, OpenIB group, how to you plan to address this issue? Do you all
> have a position as to how you think your code base can be accepted into
> the main kernel tree given these recent events?
Well, we non-vendors have no power, and it appears the vendors are
determined to kill IB.
This is all very discouraging. A lot of people at the Labs put a lot of
work into the Infiniband openib effort, including getting money to support
the software development, and it looks like we're not going to get very
far if these rules stick. I am going to renew my search for non-IB
solutions, I guess. It's hard to recommend this interconnect when IBTA
takes this kind of action.
ron
next prev parent reply other threads:[~2004-10-08 20:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 20:22 Greg KH
2004-10-08 20:38 ` Ronald G. Minnich [this message]
2004-10-08 22:49 ` [openib-general] " Eric W. Biederman
2004-10-08 23:13 ` Greg KH
2004-10-08 23:24 ` Lee Revell
2004-10-08 23:26 ` Dave Jones
2004-10-08 23:29 ` Roland Dreier
2004-10-08 23:13 ` Jeff Garzik
2004-10-08 23:27 ` Roland Dreier
2004-10-08 23:34 ` Greg KH
2004-10-09 3:40 ` Roland Dreier
2004-10-09 0:57 ` Jeff Garzik
2004-10-09 3:09 ` Roland Dreier
2004-10-09 4:23 ` Jeff Garzik
2004-10-09 21:11 ` Roland Dreier
2004-10-10 19:05 ` Alan Cox
2004-10-10 20:33 ` Roland Dreier
2004-10-09 11:50 ` Francois Romieu
2004-10-09 20:47 ` Roland Dreier
2004-10-22 23:59 ` Troy Benjegerdes
[not found] ` <6.1.2.0.2.20041008152933.01f671a8@esmail.cup.hp.com>
2004-10-11 18:27 ` Ronald G. Minnich
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=Pine.LNX.4.58.0410081428230.9700@linux.site \
--to=rminnich@lanl.gov \
--cc=greg@kroah.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 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®