Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752165AbaDXUBS (ORCPT ); Thu, 24 Apr 2014 16:01:18 -0400 Received: from mail-qg0-f54.google.com ([209.85.192.54]:57141 "EHLO mail-qg0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751265AbaDXUBQ (ORCPT ); Thu, 24 Apr 2014 16:01:16 -0400 MIME-Version: 1.0 In-Reply-To: References: <530F0C4F.9030200@mellanox.com> <531F1550.3080401@mellanox.com> Date: Thu, 24 Apr 2014 23:01:15 +0300 Message-ID: Subject: Re: [PATCH] mlx4: Use GFP_NOFS calls during the ipoib TX path when creating the QP From: Or Gerlitz To: Jiri Kosina Cc: Or Gerlitz , Roland Dreier , Sagi Grimberg , Amir Vadai , Eli Cohen , Eugenia Emantayev , "David S. Miller" , Mel Gorman , "netdev@vger.kernel.org" , linux-kernel , Saeed Mahameed , Shlomo Pongratz Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 24, 2014 at 8:03 PM, Jiri Kosina wrote: > > On Tue, 11 Mar 2014, Or Gerlitz wrote: [...] > > > So sounds like a plan that makes sense? > > Hi everybody, seems like this fell through cracks, Hi Jiri, I sent you private note on Mar 19th saying "are you on track with this for 3.15? the merge window is coming soon and you have 99% of what you need -- lets get there" which seems to be the piece that fell between the cracks. > > probably because it wasn't clearly stated *who* will be preparing patch(es) that'd be implementing the ideas above. My understanding was that it'd be Mellanox, given that they basically own the driver, to be precise partially own the mlx4 HW driver (Roland is the mlx4_core/ib author and maintainer, we are asking for few years to get co-maintainer hat there, no success so far), the problem you have described can happen with any HW driver, but as stated earlier, the suggested plan will fix ipoib and mlx4 and following that more hw drivers can be enhanced to support that too. > > have the best testing coverage compared to very very limited > testing coverage I can do, and will be pushing it upstream anyway. > > I believe all the above can be easily created on top of the original patch I sent. Indeed, so will take a look next week and let you know if it works for me > > > So ... was there a misunderstanding on who is going to do it? :) > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/