From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f65.google.com ([74.125.83.65]:37890 "EHLO mail-pg0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754530AbeCPQSe (ORCPT ); Fri, 16 Mar 2018 12:18:34 -0400 Subject: Re: [PATCH v2 iproute2-next 0/6] cm_id, cq, mr, and pd resource tracking To: Doug Ledford , Leon Romanovsky , stephen@networkplumber.org Cc: Steve Wise , netdev@vger.kernel.org, linux-rdma@vger.kernel.org References: <0b9901d3ba15$1ac4a1d0$504de570$@opengridcomputing.com> <87cc06e1-0e54-12f7-a9b0-326e568c3d6f@gmail.com> <20180313083211.GB1080@mtr-leonro.local> <1520974685.18703.11.camel@redhat.com> From: David Ahern Message-ID: <3dc4d0e2-1435-6455-34d8-4a9d13b010c4@gmail.com> Date: Fri, 16 Mar 2018 09:18:31 -0700 MIME-Version: 1.0 In-Reply-To: <1520974685.18703.11.camel@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org List-ID: On 3/13/18 1:58 PM, Doug Ledford wrote: > On Tue, 2018-03-13 at 13:45 -0700, David Ahern wrote: >> On 3/13/18 1:32 AM, Leon Romanovsky wrote: >>> On Mon, Mar 12, 2018 at 10:53:03AM -0700, David Ahern wrote: >>>> On 3/12/18 8:16 AM, Steve Wise wrote: >>>>> Hey all, >>>>> >>>>> The kernel side of this series has been merged for rdma-next [1]. Let me >>>>> know if this iproute2 series can be merged, of if it needs more changes. >>>>> >>>> >>>> The problem is that iproute2 headers are synced to kernel headers from >>>> DaveM's tree (net-next mainly). I take it this series will not appear in >>>> Dave's tree until after a merge through Linus' tree. Correct? >>> >>> David, >>> >>> Technically, you are right, and we would like to ask you for an extra tweak >>> to the flow for the RDMAtool, because current scheme causes delays at least >>> cycle. >>> >>> Every RDMAtool's patchset which requires changes to headers is always >>> includes header patch, can you please accept those series and once you >>> are bringing new net-next headers from Linus, simply overwrite all our >>> headers? >> >> I did not follow the discussion back when this decision was made, so how >> did rdma tool end up in iproute2? > > It is modeled after the ip command, and for better or worse, the > iproute2 package has become the standard drop box for low level kernel > network configuring tools. The RDMA subsystem may not be IP networking, > but it is still networking, so it seemed an appropriate fit. why doesn't the rdma tree go through Dave then?