Hello Rolland, Thanks for reviewing the port mapper patches.
Steve's reply is correct. Unpatched nes will not regress and will continue working as before. Tatyana -----Original Message----- From: Steve Wise [mailto:sw...@opengridcomputing.com] Sent: Tuesday, May 20, 2014 8:45 AM To: 'Roland Dreier'; Nikolova, Tatyana E Cc: Lacombe, John S; Hefty, Sean; linux-rdma@vger.kernel.org; 'Doug Ledford' Subject: RE: [PATCH 0/3] RDMA/core: iWARP Port Mapper Overview > -----Original Message----- > From: linux-rdma-ow...@vger.kernel.org > [mailto:linux-rdma-ow...@vger.kernel.org] On Behalf Of Roland Dreier > Sent: Monday, May 19, 2014 8:10 PM > To: Tatyana Nikolova > Cc: Lacombe, John S; Steve Wise; Sean Hefty; > linux-rdma@vger.kernel.org > Subject: Re: [PATCH 0/3] RDMA/core: iWARP Port Mapper Overview > > On Wed, Mar 26, 2014 at 3:07 PM, Tatyana Nikolova > <tatyana.e.nikol...@intel.com> wrote: > > 1) The IWPM functionality, common for both iWarp drivers (nes and cxgb4) > > is refactored from the drivers source files and is moved to new shared > > files in infiniband/core which are compiled as part of the iw_cm module. > > > So I'm looking to include this for 3.16. One question: I assume > unpatched iwarp drivers (eg cxgb3) continue to work as before? In > other words they don't get the new port mapper support but at least > they don't regress? > Hey Roland, cxgb3<->cxgb3 would behave as before; no regression. cxgb3<->cxgb4/nes would interoperate only if the port mapping service is disabled on the cxgb4/nes nodes. Steve. N�����r��y����b�X��ǧv�^�){.n�+����{��ٚ�{ay� ʇڙ�,j��f���h���z� �w��� ���j:+v���w�j�m��������zZ+�����ݢj"��!�i
