Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753768AbaBYWko (ORCPT ); Tue, 25 Feb 2014 17:40:44 -0500 Received: from cantor2.suse.de ([195.135.220.15]:60037 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753732AbaBYWkk (ORCPT ); Tue, 25 Feb 2014 17:40:40 -0500 Date: Tue, 25 Feb 2014 23:40:35 +0100 (CET) From: Jiri Kosina To: Or Gerlitz cc: Roland Dreier , Amir Vadai , Eli Cohen , Or Gerlitz , Eugenia Emantayev , "David S. Miller" , Mel Gorman , "netdev@vger.kernel.org" , linux-kernel Subject: Re: [PATCH] mlx4: Use GFP_NOFS calls during the ipoib TX path when creating the QP In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 26 Feb 2014, Or Gerlitz wrote: > >> And what happens if you use IPoIB datagram mode, is/why the patch is > >> needed there? > > > I admittedly am no infiniband expert, but my understanding is that in > > principle Connected/Datagram mode is about MTU and checksum offloading, > > yes, the differences between the mode relate to these aspects, however Thanks for confirming. > > but the TX path is the same. Please correct me if I am wrong. > > no, note that your patch only touched drivers/infiniband/ulp/ipoib/ipoib_cm.c > which is basically compiled out if you set CONFIG_INFINIBAND_IPOIB_CM, > so surely the TX path for the datagram vs. connected modes are > different. Yes, but for datagram mode, the tx_ring is allocated in a completely different way (not from kworker), so this might be a non-issue, right? I will have to look into it more deeply to be really sure; if you can provide your insight, that'd be helpful. -- Jiri Kosina SUSE Labs -- 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/