Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751966AbaBFX7Z (ORCPT ); Thu, 6 Feb 2014 18:59:25 -0500 Received: from mail.linux-iscsi.org ([67.23.28.174]:44744 "EHLO linux-iscsi.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751494AbaBFX7X (ORCPT ); Thu, 6 Feb 2014 18:59:23 -0500 Message-ID: <1391731323.14985.56.camel@haakon3.risingtidesystems.com> Subject: Re: linux rdma 3.14 merge plans From: "Nicholas A. Bellinger" To: Roland Dreier Cc: Or Gerlitz , Hefty Sean , linux-rdma , "Martin K. Petersen" , target-devel , Sagi Grimberg , linux-kernel Date: Thu, 06 Feb 2014 16:02:03 -0800 In-Reply-To: <1390375658.5567.917.camel@haakon3.risingtidesystems.com> References: <52CD1C68.4050406@mellanox.com> <1389645171.5567.459.camel@haakon3.risingtidesystems.com> <1389820541.5567.543.camel@haakon3.risingtidesystems.com> <1389906852.5567.668.camel@haakon3.risingtidesystems.com> <1390102949.5567.749.camel@haakon3.risingtidesystems.com> <52DBB4F1.4020400@mellanox.com> <1390375658.5567.917.camel@haakon3.risingtidesystems.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.4.4-1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Roland, On Tue, 2014-01-21 at 23:27 -0800, Nicholas A. Bellinger wrote: > Roland & Co, > > On Tue, 2014-01-21 at 16:43 -0800, Roland Dreier wrote: > > On Tue, Jan 21, 2014 at 2:00 PM, Or Gerlitz wrote: > > > Roland, ping! the signature patches were posted > three months ago. We > > > deserve a response from the maintainer that goes beyond "I need to > > > think on that". > > > > > > Responsiveness was stated by Linus to be the #1 requirement from > > > kernel maintainers. > > > > Or, I'm not sure what response you're after from me. Linus has also > > said that maintainers should say "no" a lot more > > (http://lwn.net/Articles/571995/) so maybe you want me to say, "No, I > > won't merge this patch set, since it adds a bunch of complexity to > > support a feature no one really cares about." Is that it? > > The patch set proposed by Sagi + Or is modest in terms of LOC to core IB > code, and includes mostly mlx5 specific driver changes that enables HW > offloads. > > > (And yes I > > am skeptical about this stuff — I work at an enterprise storage > > company and even here it's hard to find anyone who cares about > > DIF/DIX, especially offload features that stop it from being > > end-to-end) > > > > My understanding is most HBAs capable of T10 PI offload in DIX PASS + > VERIFY mode are already implementing DIX INSERT + STRIP modes in various > capacities to support legacy environments. > > Beyond the DIX INSERT + STRIP case for enterprise storage, the amount of > FC + SAS HBAs that already support T10 PI metadata is substantial. > > > I'm sure you're not expecting me to say, "Sure, I'll merge it without > > understanding the problem it's solving or how it's doing that," > > especially given the your recent history of pushing me to merge stuff > > like the IP-RoCE patches back when they broke the userspace ABI. > > With the merge window now upon us, there is a understandable reluctance > to merge new features. Given the amount of time the series has spent on > the list, it is however a good candidate to consider for an exception. > > Short of that, are you planning to accept the series for the next round > once the current merge window closes..? > > We'd really like to start enabling fabrics with these types of offloads > for v3.15. > Now with the initial DIF backend taraget support in place for v3.14-rc1 code, we'd like to move forward on iser-target related pieces for T10 PI. Can you give us an estimate of when you'll have some time to give feedback on the outstanding patches..? --nab -- 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/