From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Wise Subject: Re: [ofa-general] [PATCH v3] iw_cxgb3: Support"iwarp-only"interfacesto avoid 4-tuple conflicts. Date: Fri, 28 Sep 2007 16:27:06 -0500 Message-ID: <46FD71AA.8070901@opengridcomputing.com> References: <20070923203649.8324.64524.stgit@dell3.ogc.int><46FBF8AF.9040700@ichips.intel.com> <000101c8013a$41b374f0$a7cc180a@amr.corp.intel.com> <46FD5A2F.7010409@opengridcomputing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Sean Hefty , Sean Hefty , netdev@vger.kernel.org, rdreier@cisco.com, linux-kernel@vger.kernel.org, general@lists.openfabrics.org To: "Kanevsky, Arkady" Return-path: Received: from 209-198-142-2-host.prismnet.net ([209.198.142.2]:43169 "EHLO smtp.opengridcomputing.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751397AbXI1V1G (ORCPT ); Fri, 28 Sep 2007 17:27:06 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Kanevsky, Arkady wrote: > Exactly, > it forces the burden on administrator. > And one will be forced to try one mount for iWARP and it does not > work issue another one TCP or UDP if it fails. > Yack! > I see your point. I have no defense. My hands have been tied on fixing this properly... > And server will need to listen on different IP address and simple > * will not work since it will need to listen in two different domains. > No, the server will listen on 0.0.0.0:2049 for TCP, and 0.0.0.0:2050 for rdma. The rdma subsystem will translate 0.0.0.0:2050 into listens on specific iwarp ip addresses on every iwarp device... > Had we run this proposal by administrators? There has been no other solution proposed that Dave Miller and Jeff Garzik won't NAK... Steve.