Re: PATCH - InfiniBand Access Layer (IBAL)

[Roland Dreier <roland@topspin.com>]

    Ulrich> The only acceptable order in which things can happen is:

    Ulrich> 1. develop API
    Ulrich> 2. propose API to be accepted by "community"/distributions
    Ulrich> 3. change API if necessary, and go back to 2.
    Ulrich> 4. write applications using new API

I don't think this is reasonable, since nothing is settled enough for
this to work.  On the one hand, InfiniBand and other "fibers" (eg RDMA
over ethernet) are quite experimental.  No one is sure of the right
semantics or the best way to use the interconnect.  On the other hand,
there are people who want to use this stuff right now (eg
high-performance computing people building clusters, database cluster
people, etc).

There are users who want to use InfiniBand now, and making them wait
through your whole process above is simply untenable.  You can't
expect a company selling InfiniBand equipment to say, "Sorry, our
software isn't perfect (although it would work for you now).  Come
back in a year or two."

With that in mind, I think the only order things can happen is:

    1. develop API
    2. implement API
    2a.learn from mistakes and go back to 1.
    3. write applications using API
    4. learn from mistakes and go back to 1.

It's certainly unfortunate that so much InfiniBand software has been
developed behind closed doors, but the industry has finally woken up
and come together around the OpenIB idea to develop Linux support
completely in the open.

When does this software make it into distributions?  Obviously that's
up to the distribution.  Certainly a commercial distribution has
customers of its own to listen to, and I would assume that the
decision would be made based on the appropriate combination of
technical merit and customer demand.

 - Roland