[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1828884A29C6694DAF28B7E6B8A82373A8FC1C7C@ORSMSX109.amr.corp.intel.com>
Date: Wed, 15 Apr 2015 19:29:31 +0000
From: "Hefty, Sean" <sean.hefty@...el.com>
To: Hal Rosenstock <hal@....mellanox.co.il>,
Michael Wang <yun.wang@...fitbricks.com>
CC: Roland Dreier <roland@...nel.org>,
Hal Rosenstock <hal.rosenstock@...il.com>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Tom Tucker <tom@...ngridcomputing.com>,
Steve Wise <swise@...ngridcomputing.com>,
Hoang-Nam Nguyen <hnguyen@...ibm.com>,
Christoph Raisch <raisch@...ibm.com>,
infinipath <infinipath@...el.com>, Eli Cohen <eli@...lanox.com>,
"Latif, Faisal" <faisal.latif@...el.com>,
Jack Morgenstein <jackm@....mellanox.co.il>,
"Or Gerlitz" <ogerlitz@...lanox.com>,
Haggai Eran <haggaie@...lanox.com>,
"Weiny, Ira" <ira.weiny@...el.com>, Tom Talpey <tom@...pey.com>,
Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
Doug Ledford <dledford@...hat.com>
Subject: RE: [PATCH v3 01/28] IB/Verbs: Implement new callback
query_transport()
> 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
Powered by blists - more mailing lists