From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com ([209.132.183.28]:51786 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751186AbeCTRVd (ORCPT ); Tue, 20 Mar 2018 13:21:33 -0400 Subject: Re: [PATCH v2 iproute2-next 0/6] cm_id, cq, mr, and pd resource tracking To: David Ahern , 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> <3dc4d0e2-1435-6455-34d8-4a9d13b010c4@gmail.com> From: Doug Ledford Message-ID: Date: Tue, 20 Mar 2018 13:21:28 -0400 MIME-Version: 1.0 In-Reply-To: <3dc4d0e2-1435-6455-34d8-4a9d13b010c4@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="kw4k4a0QvKBoY969bwDKWLlJg9UJKJQzP" Sender: netdev-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --kw4k4a0QvKBoY969bwDKWLlJg9UJKJQzP Content-Type: multipart/mixed; boundary="qP785vdXtc9yp2K4I3qjQH0gQy9xEUfv3"; protected-headers="v1" From: Doug Ledford To: David Ahern , Leon Romanovsky , stephen@networkplumber.org Cc: Steve Wise , netdev@vger.kernel.org, linux-rdma@vger.kernel.org Message-ID: Subject: Re: [PATCH v2 iproute2-next 0/6] cm_id, cq, mr, and pd resource tracking References: <0b9901d3ba15$1ac4a1d0$504de570$@opengridcomputing.com> <87cc06e1-0e54-12f7-a9b0-326e568c3d6f@gmail.com> <20180313083211.GB1080@mtr-leonro.local> <1520974685.18703.11.camel@redhat.com> <3dc4d0e2-1435-6455-34d8-4a9d13b010c4@gmail.com> In-Reply-To: <3dc4d0e2-1435-6455-34d8-4a9d13b010c4@gmail.com> --qP785vdXtc9yp2K4I3qjQH0gQy9xEUfv3 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 3/16/2018 12:18 PM, David Ahern wrote: > 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 ch= anges. >>>>>> >>>>> >>>>> The problem is that iproute2 headers are synced to kernel headers f= rom >>>>> DaveM's tree (net-next mainly). I take it this series will not appe= ar 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 extr= a tweak >>>> to the flow for the RDMAtool, because current scheme causes delays a= t least >>>> cycle. >>>> >>>> Every RDMAtool's patchset which requires changes to headers is alway= s >>>> includes header patch, can you please accept those series and once y= ou >>>> are bringing new net-next headers from Linus, simply overwrite all o= ur >>>> 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 networkin= g, >> but it is still networking, so it seemed an appropriate fit. >=20 > why doesn't the rdma tree go through Dave then? >=20 Because it doesn't use the core network stack hardly at all. It creates netdevs when it needs to bridge the two stacks, but otherwise the RDMA subsystem core is apart and unique from the network stack Dave manages. When I said it was networking, I meant it literally. The RDMA fabrics are networks. It wasn't meant to imply that they shared anything substantial in common with the typical Ethernet/IP networking that is the core of what Dave manages. --qP785vdXtc9yp2K4I3qjQH0gQy9xEUfv3-- --kw4k4a0QvKBoY969bwDKWLlJg9UJKJQzP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIzBAEBCAAdFiEErmsb2hIrI7QmWxJ0uCajMw5XL90FAlqxQxgACgkQuCajMw5X L92ZMhAAgfdln5W2tC6PP001lsKK59KSfNlKi7oACcMk+KF/FJZKNLVaTGDjzwL6 ZWLYp2puZLxuf04bHE1QLv+nWyRiO/7h0BKSL2iEXzUbmwvaKMppoYF+f/Xuqx6T LvF95690NpeSi34hbGdnkGrRjfgmbtujtd8fQvpcDFXAksbvATq5Ij/3nwS/8b4v 1XsZB5VTY8EryiuA2CRL/PNG6qquzpEyDqao5qYGAUDiff/LD/NEbtwSH5+aqnde ZXq9moZ2mWdwyjsQW1ITC5a/eyhpyKberqRoaP5IYomfubV3ALE81YUKIOulTz53 rK757hZQ48GydpRuphK4itZSVsXSmFM5Mo1hf7elNdzUbd+tQLBi1n1/BopOIDbu 1uHLk5C4smasgObeGACyCjgmTGLIxtJl/2KVd+ugTNy725OGRtCqGz/LaPkF3R75 M1RaAraAuxJ535+V8wiNr5SVO5H5WGmIg5d2GIiKVrfI1ZNyHhXauhM3tt98WyXD KotsQzueR1mubFr3yZu69uVrsrPCooeflzlWZR0hTeSNL1UfkEBq6fyzi7JLh+1L OXaXKccxYw6UcHckYud5L4ah1M6Lb8v5a/n+JXV8v3FOAIbLZGjFfdZAFwC2cIb8 SCDpX1nNbLX7eiWJTULh/FsHqdt7zH6G2BXU+z1z5O3t4VadFW8= =MynL -----END PGP SIGNATURE----- --kw4k4a0QvKBoY969bwDKWLlJg9UJKJQzP--