From: Roland Dreier <roland@topspin.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: "Woodruff, Robert J" <woody@co.intel.com>,
"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>
Subject: Re: PATCH - InfiniBand Access Layer (IBAL)
Date: 19 Mar 2004 12:47:45 -0800 [thread overview]
Message-ID: <52oeqs4l8u.fsf@topspin.com> (raw)
In-Reply-To: <405B403F.4000702@redhat.com>
Ulrich> I think I should be telling something about another nuance
Ulrich> of this problem. Parties interested in Infiniband have
Ulrich> been working under the OpenGroup umbrella for quite some
Ulrich> time now on API extensions to better accommodate
Ulrich> interconnect fibers. They've even presented at am Austin
Ulrich> Group meeting in 2001 (I think) to get on the road map for
Ulrich> being included in POSIX.
Ulrich> But when I wanted to take a look at the specs this was
Ulrich> categorically rejected. My contacts were explicitly
Ulrich> forbidden to give the drafts to anybody but the elite
Ulrich> circle. Mind you, Red Hat is member of the OpenGroup.
Ulrich> So, these people come up with their own software stacks,
Ulrich> unreviewed interface extensions, and demand that everybody
Ulrich> accepts what they were "designing" without the ability to
Ulrich> question anything.
Ulrich> I surely find this completely unacceptable and any
Ulrich> consideration of accepting anything the Infiniband group
Ulrich> comes up with should be postponed until every bit of the
Ulrich> design can be reviewed. If bits and pieces are accepted
Ulrich> prematurely it'll just be "now that this is support you
Ulrich> have to add this too, otherwise it'll not be useful".
I believe what you are referring to is the OpenGroup's "ITAPI" work.
This is in a sense a competing spec to the DAT Collaborative
(www.datcollaborative.org) work. The DAT Collaborative seems to be
far more open, and their spec is available without any hurdles.
Any demands from groups designing unacceptable specs should be treated
with the appropriate level of cooperation.
Note that neither the OpenGroup nor the DAT Collaborative are
affiliated with the InfiniBand Trade Association or the OpenIB group,
although they may have members in common.
Best,
Roland
next prev parent reply other threads:[~2004-03-19 20:48 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 22:52 PATCH - InfiniBand Access Layer (IBAL) 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 [this message]
-- 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-14 23:14 Nivedita Singhvi
2004-03-14 3:46 Woodruff, Robert J
2004-03-15 2:10 ` Greg KH
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=52oeqs4l8u.fsf@topspin.com \
--to=roland@topspin.com \
--cc=arlin.r.davis@intel.com \
--cc=drepper@redhat.com \
--cc=jerrie.l.coffman@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sean.hefty@intel.com \
--cc=woody@co.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).