From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx3-rdu2.redhat.com ([66.187.233.73]:38712 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752800AbeCMU6H (ORCPT ); Tue, 13 Mar 2018 16:58:07 -0400 Message-ID: <1520974685.18703.11.camel@redhat.com> Subject: Re: [PATCH v2 iproute2-next 0/6] cm_id, cq, mr, and pd resource tracking From: Doug Ledford To: David Ahern , Leon Romanovsky , stephen@networkplumber.org Cc: Steve Wise , netdev@vger.kernel.org, linux-rdma@vger.kernel.org Date: Tue, 13 Mar 2018 16:58:05 -0400 In-Reply-To: References: <0b9901d3ba15$1ac4a1d0$504de570$@opengridcomputing.com> <87cc06e1-0e54-12f7-a9b0-326e568c3d6f@gmail.com> <20180313083211.GB1080@mtr-leonro.local> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-SH3X8ASl5uOhwMVBaJaO" Mime-Version: 1.0 Sender: netdev-owner@vger.kernel.org List-ID: --=-SH3X8ASl5uOhwMVBaJaO Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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, > > > >=20 > > > > 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 cha= nges. > > > >=20 > > >=20 > > > The problem is that iproute2 headers are synced to kernel headers fro= m > > > 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? > >=20 > > David, > >=20 > > Technically, you are right, and we would like to ask you for an extra t= weak > > to the flow for the RDMAtool, because current scheme causes delays at l= east > > cycle. > >=20 > > 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? >=20 > 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. > I do not need the overhead of > sometimes I sync the rdma header file and sometimes I don't. >=20 > One option that comes to mind is to move the rdma header file under the > rdma directory. It breaks the uapi model, but it seems that iproute2 is > just a delivery vehicle for this command. --=20 Doug Ledford GPG KeyID: B826A3330E572FDD Key fingerprint =3D AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD --=-SH3X8ASl5uOhwMVBaJaO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEErmsb2hIrI7QmWxJ0uCajMw5XL90FAlqoO10ACgkQuCajMw5X L933RA//VxjdHbnZw8ZnTnBJ2BTjsjHytnv6n8vw4w6DXMIn5+0hKyqrKtfWTCw3 bF8sT6ufroCvHNyVDiq/hV6AdWaAoIp4FKd/NT94T5MqBOOKZJbOAVgThPFrYPw5 j3oUqixdRZZ6ZgVyW21bTUGPXOCie1Icyq7d2hBeeHr3dXzTQOEhAMVMZf2H2FUI /WLSpM9Q0KuxmqjqgbRiUiMgWDHvrAnuRO2Rq5fZ7e0fp4xe4R9XE2+69bXxxzgB GCNR35mrb+cwC43c9tStBeDmg5sJaDtAEr4XPT6OeEuHXFv29IFXtUEh/QxtPtfT s+VrfvKqv+5pM41qtnOXjFttV6o5HmCyS4BqtGGyZ95TwvbWjr1LROHBgwgHyO4E XCrSGZOkyEjiqT7kXGz7HUHLC5ZB+sEf+fCGqvbE8xgWJ77dFIvGcdELgDtkZMHM MDCJdLMJyoO1FCSc5QaYBjOsjlaWp0krxqx8QFMwhOPjYbKeA3bCxD4uQFDZDbo3 TqhKVEA97pcbowXDc+JAc02qM/889yffCt0DQdVLG/i16wrBts9pgBBZ3bh1F7jY 1j8yY/W0ujIL8IEkqPzrbRv7ZvlNO28hWJ0XayIH0eAWjogkt+FLFbc9cin7UoBL NTHjtMqjasQSDuEnVoF3/ut7t3yALu4Kd/Phfjteh4yinsUnH8Y= =ha+T -----END PGP SIGNATURE----- --=-SH3X8ASl5uOhwMVBaJaO--