Return-Path: Received: from mail-wi0-f179.google.com ([209.85.212.179]:36424 "EHLO mail-wi0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753293AbbCaN65 (ORCPT ); Tue, 31 Mar 2015 09:58:57 -0400 Received: by wixo5 with SMTP id o5so14816122wix.1 for ; Tue, 31 Mar 2015 06:58:56 -0700 (PDT) Message-ID: <551AA81C.30701@profitbricks.com> Date: Tue, 31 Mar 2015 15:58:52 +0200 From: Michael Wang MIME-Version: 1.0 To: Tom Talpey , Jason Gunthorpe CC: "ira.weiny" , Roland Dreier , Sean Hefty , Hal Rosenstock , linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org, netdev@vger.kernel.org, "J. Bruce Fields" , Trond Myklebust , "David S. Miller" , Or Gerlitz , Moni Shoua , PJ Waskiewicz , Tatyana Nikolova , Yan Burman , Jack Morgenstein , Bart Van Assche , Yann Droneaud , Colin Ian King , Majd Dibbiny , Jiri Kosina , Matan Barak , Alex Estrin , Doug Ledford , Eric Dumazet , Erez Shitrit , Sagi Grimberg , Haggai Eran , Shachar Raindel , Mike Marciniszyn , Steve Wise , Tom Tucker , Chuck Lever Subject: Re: [RFC PATCH 08/11] IB/Verbs: Use management helper has_iwarp() for, iwarp-check References: <551579CA.4030901@profitbricks.com> <55157B98.1060103@profitbricks.com> <20150327161319.GB28412@obsidianresearch.com> <20150327171631.GC27862@phlsvsds.ph.intel.com> <20150327172912.GA28901@obsidianresearch.com> <55196754.5010600@profitbricks.com> <20150330223528.GB27728@obsidianresearch.com> <551A4F24.6090405@profitbricks.com> <551A82D3.70806@talpey.com> <551A87D3.2070306@profitbricks.com> <551AA78D.4040502@talpey.com> In-Reply-To: <551AA78D.4040502@talpey.com> Content-Type: text/plain; charset=windows-1252 Sender: linux-nfs-owner@vger.kernel.org List-ID: On 03/31/2015 03:42 PM, Tom Talpey wrote: > On 3/31/2015 7:41 AM, Michael Wang wrote: >> [snip] > Yes, in fact the iWARP protocol does not preclude multiple read SGEs, > even though most iWARP implementations have chosen to support just one. > > Even for multi-SGE-capable adapters, there is a limit of SGL size, based > on the adapter's work request format and other factors. So my argument > is that upper layers can and should query that, not make a blanket > decision based on protocol type. Thanks for the explanation Sounds like some new callback on device level like query_device() to acquire the right info. >> I currently only find this one place where infer max-read-sges from >> transport type, it looks more like a special case to me rather than a generic >> method we could exposed... and also not very related with IB management >> helper concept IMHO. > It is most certainly not a special case, but you could decide to > introduce it in many ways. I'm not commenting on that. > > My main concern is that you do not introduce a new and clumsy "is iWARP" > rule as an adapter-specific API requirement to expose the RDMA Read SGE > behavior. That's what your initial message seemed to imply? Yeah I planed to just use rdma_transport_iwarp() to replace the check, it's actually meaningless but just refine, frankly speaking I would prefer some driver developer to work on that part, at this point I prefer to focus on introducing the management helpers firstly Maybe we could mark it as a TODO temporarily, if later we found more scenes using similar logical, we can collect them and do some reform Regards, Michael Wang