> I understand your frustration in having to deal with a large amount
> of code. If you included all the Mellanox firmware in the mlx4
> driver, it would be huge too. I'm limited in what I can do given
> the complexity of the IBTA spec.
Sure, I understand that your driver is going to be prett
> > - mlx4 SR-IOV support. Again, main problem was my lack of time. I
> > agree in principle with this stuff, just want to be careful that we
> > don't turn the mlx4 driver into an unmaintainable mess of "if
> > (sriov) something; else something_else" all over.
> Roland,
> Y
On 12/14/2009 8:37 PM, Roland Dreier wrote:
- mlx4 SR-IOV support. Again, main problem was my lack of time. I
agree in principle with this stuff, just want to be careful that we
don't turn the mlx4 driver into an unmaintainable mess of "if
(sriov) something; else something_else"
Eli Cohen wrote:
- IBoE. In principle I think this is starting to get there. Still
want to see better ABI compatibility at least, and also make sure
the interface chosen works for both rdmacm and non-rdmacm applications.
Based on this, I am going to send a new patch set, a few days
On Mon, Dec 14, 2009 at 10:37:40AM -0800, Roland Dreier wrote:
>
> Here are a few topics that are not ready in time for the 2.6.33 window
> and will need to wait for 2.6.34 at least:
>
>
> - IBoE. In principle I think this is starting to get there. Still
>want to see better ABI compatibil
On Mon, 2009-12-14 at 10:37 -0800, Roland Dreier wrote:
> - New QLogic qib driver. Needs at least one more iteration of
>cleanups; and I have not had time to look at the latest code in
>detail to see exactly what cleanups are needed. I am concerned
>that QLogic chose to abandon the
Since 2.6.32 is already out, it's probably a good time (or at least I
shouldn't wait longer!) to talk about 2.6.33 merge plans.
Unfortunately I lost pretty much a week and a half after Thanksgiving
to the flu, so I'm pretty late and didn't get as much done as I hoped.
Anyway, all the pending things
