public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Eric W. Biederman" <ebiederman@lnxi.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 16:13:07 -0700	[thread overview]
Message-ID: <20041008231307.GA32530@kroah.com> (raw)
In-Reply-To: <m3d5zs966r.fsf@maxwell.lnxi.com>

On Fri, Oct 08, 2004 at 04:49:16PM -0600, Eric W. Biederman wrote:
> Greg KH <greg@kroah.com> writes:
> 
> > [2] Sure, any person who has a copy of the kernel source tree could be a
> > target for any of a zillion other potential claims, nothing new there,
> > but the point here is they are explicitly stating that they will go
> > after non-IBTA members who touch IB code[3].
> 
> Greg I see nothing to back up the idea that IBTA intends to go after
> non-members.  I simply see a disclaimer of warranty, and I see wording
> by your anonymous source that restates a disclaimer of warranty.

All I know is a number of different people, from different companies are
suddenly very worried about this.  The fact that they don't want to
comment on it in public leads me to believe that there is something
behind their fears.

> Until I see something more to back this up I do not see a problem.  In
> fact I see infiniband prices dropping, and competition increasing.
> The drivers off of openib.org look like they are a good start at
> making a sane linux implementation.

It is a good start.  And as all OpenIB members are also IBTA members, I
am asking for the group's position as to this change.

> Even the PCI-SIG requires you to pay for the spec.

I know that, almost all groups do.  Although $9500 does seem a bit steep
for spec prices :)

> I agree it would be suicidally insane for the infiniband trade
> association to go after a linux stack, as it appears that a large
> portion of the infiniband users are currently running linux.

One specific IBTA member has issues with the adaption of Linux, and has
already done one thing to restrict a full IB implementation that would
work on Linux.  And as for insane, have you ever tried to actually read
that spec?  :)

thanks,

greg k-h

  reply	other threads:[~2004-10-08 23:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08 20:22 InfiniBand incompatible with the Linux kernel? Greg KH
2004-10-08 20:38 ` [openib-general] " Ronald G. Minnich
2004-10-08 22:49 ` Eric W. Biederman
2004-10-08 23:13   ` Greg KH [this message]
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=20041008231307.GA32530@kroah.com \
    --to=greg@kroah.com \
    --cc=ebiederman@lnxi.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