On Wed, 26 Feb 2014, Or Gerlitz wrote: > > But let's make sure that we don't diverge from the original problem too > > much. Simple fact is that the deadlock is there when using connected mode, > > and there is nothing preventing users from using it this way, therefore I > > believe it should be fixed one way or another. > > the patch is titled with "mlx4:" -- do you expect the problem to come > into play only when ipoib connected mode runs over the mlx4 driver? > what's about mlx5 or other upstream IB drivers?
Honestly, I have no idea. I am pretty sure that Mellanox folks have much better understanding of the mlx* driver internals than I do. I tried to figure out where mlx5 is standing in this respect, but I don't even see where ipoib_cm_tx->tx_ring is being allocated there. > I'll be looking on the details of the problem/solution, Awesome, thanks a lot, that's highly appreciated. > Do we have a way to tell a net-device instance they should do their > memory allocations in a NOFS manner? if not, shouldn't we come up with > more general injection method? I don't think we have, and it indeed should be rather easy to add. The more challenging part of the problem is where (and based on which data) the flag would actually be set up on the netdevice so that it's not horrible layering violation. -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
