lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 27 Sep 2007 16:19:51 -0400
From:	"Kanevsky, Arkady" <Arkady.Kanevsky@...app.com>
To:	"Sean Hefty" <sean.hefty@...el.com>,
	"Sean Hefty" <mshefty@...ips.intel.com>,
	"Steve Wise" <swise@...ngridcomputing.com>
Cc:	<netdev@...r.kernel.org>, <rdreier@...co.com>,
	<linux-kernel@...r.kernel.org>, <general@...ts.openfabrics.org>
Subject: RE: [ofa-general] [PATCH v3] iw_cxgb3: Support"iwarp-only"interfacesto avoid 4-tuple conflicts.

Sean,
IB aside,
it looks like an ULP which is capable of being both RDMA aware and RDMA
not-aware,
like iSER and iSCSI, NFS-RDMA and NFS, SDP and sockets, 
will be treated as two separete ULPs.
Each has its own IP address, since there is a different IP address for
iWARP
port and "regular" Ethernet port. So it falls on the users of ULPs to
"handle" it
via DNS or some other services.
Is this "acceptable" to users? I doubt it.

Recall that ULPs are going in opposite directions by having a different
port number for RDMA aware and RDMA unaware versions of the ULP.
This way, ULP "connection manager" handles RDMA-ness under the covers,
while users plug an IP address for a server to connect to.
Thanks,

Arkady Kanevsky                       email: arkady@...app.com
Network Appliance Inc.               phone: 781-768-5395
1601 Trapelo Rd. - Suite 16.        Fax: 781-895-1195
Waltham, MA 02451                   central phone: 781-768-5300
 

> -----Original Message-----
> From: Sean Hefty [mailto:sean.hefty@...el.com] 
> Sent: Thursday, September 27, 2007 3:12 PM
> To: Kanevsky, Arkady; Sean Hefty; Steve Wise
> Cc: netdev@...r.kernel.org; rdreier@...co.com; 
> linux-kernel@...r.kernel.org; general@...ts.openfabrics.org
> Subject: RE: [ofa-general] [PATCH v3] iw_cxgb3: 
> Support"iwarp-only"interfacesto avoid 4-tuple conflicts.
> 
> >What is the model on how client connects, say for iSCSI, when client 
> >and server both support, iWARP and 10GbE or 1GbE, and would like to 
> >setup "most" performant "connection" for ULP?
> 
> For the "most" performance connection, the ULP would use IB, 
> and all these problems go away.  :)
> 
> This proposal is for each iwarp interface to have its own IP 
> address.  Clients would need an iwarp usable address of the 
> server and would connect using rdma_connect().  If that call 
> (or rdma_resolve_addr/route) fails, the client could try 
> connecting using sockets, aoi, or some other interface.  I 
> don't see that Steve's proposal changes anything from the 
> client's perspective.
> 
> - Sean
> _______________________________________________
> general mailing list
> general@...ts.openfabrics.org
> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general
> 
> To unsubscribe, please visit 
> http://openib.org/mailman/listinfo/openib-general
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ