Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932441AbbDOT35 (ORCPT ); Wed, 15 Apr 2015 15:29:57 -0400 Received: from mga02.intel.com ([134.134.136.20]:13861 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752040AbbDOT3w (ORCPT ); Wed, 15 Apr 2015 15:29:52 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,582,1422950400"; d="scan'208";a="556649289" From: "Hefty, Sean" To: Hal Rosenstock , Michael Wang CC: Roland Dreier , Hal Rosenstock , "linux-rdma@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Tom Tucker , Steve Wise , Hoang-Nam Nguyen , Christoph Raisch , infinipath , Eli Cohen , "Latif, Faisal" , Jack Morgenstein , "Or Gerlitz" , Haggai Eran , "Weiny, Ira" , Tom Talpey , Jason Gunthorpe , Doug Ledford Subject: RE: [PATCH v3 01/28] IB/Verbs: Implement new callback query_transport() Thread-Topic: [PATCH v3 01/28] IB/Verbs: Implement new callback query_transport() Thread-Index: AQHQdeR/TFqa5bGhHkCw9vFJSKp0bZ1O36mA//+WyRA= Date: Wed, 15 Apr 2015 19:29:31 +0000 Message-ID: <1828884A29C6694DAF28B7E6B8A82373A8FC1C7C@ORSMSX109.amr.corp.intel.com> References: <552BB470.4090407@profitbricks.com> <552BB4FA.5000109@profitbricks.com> <552EAF9D.8050400@dev.mellanox.co.il> In-Reply-To: <552EAF9D.8050400@dev.mellanox.co.il> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.139] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by nfs id t3FJU12C018155 Content-Length: 729 Lines: 10 > libibverbs also exposes transport at the device level. Isn't a change to > make transport per port rather than per device needed there as well to > be consistent with these proposed kernel changes ? If so, would the > additional IBoE transport be exposed ? We also need to worry about > backward compatibility for existing applications. Libibverbs probably can't change without bumping the major version number. If the kernel attribute structures change, this is probably something that the user_verbs module would need to handle to avoid breaking the ABI. - Sean ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?