On Fri, May 27, 2016 at 07:44:15AM -0400, Dennis Dalessandro wrote:

On Fri, May 27, 2016 at 07:51:57AM +0300, Leon Romanovsky wrote:

quoted

On Thu, May 26, 2016 at 06:34:28PM -0400, Doug Ledford wrote:

quoted

Hi Linus,

This is the second group of code for the 4.7 merge window.  It looks
large, but only in one sense.  I'll get to that in a minute.  The list
of changes here breaks down as follows:

Round two of 4.7 merge window patches

<...>

quoted

- The big item on the list: hfi1 driver updates, plus moving the hfi1
 driver out of staging                             <- everything else

Hi Doug and Linus,

The move hfi1 from the staging is a right thing, it was there a long
time and it is almost ready.

No, not almost, it is totally ready. We have bent over backwards to go well
beyond what was in the TODO list. This is a clean, stable, and well
performing driver.

It is your's TODO, not mine.

quoted

However the timing of this move puzzle me, we are in the process of ABI
change [1, 2] as a response to security alert [3]. Moves like this with
proprietary char device and ABI scheme different from whole RDMA stack
will limit the ABI work without real need.

The driver sitting in staging or not has no impact on the ABI re-design.
They are two completely separate issues.

Separate char device? IOCTLs per-device vs. global IOCTLs per subsystem?
Role of the IB CORE code in the driver management?

quoted

Will this driver be **forced** to adjust to new ABI scheme whenever it
comes? If it is not possible, the better solution to converge on ABI change will be
to leave this driver in staging/rdma and wait till proper solution will be accepted.

I think Doug has made it perfectly clear that hfi1 will need to adopt the
new ABI when it is available, and we are certainly on board with that.

It is too generic and not limited in time, I'm not against moving your
driver out of staging, just want to be sure that ABI effort won't be
limited by current hfi1 code which doesn't fit into current IB core
model.

-Denny