netdev - Re: [PATCH 3/3] bnx2i: Add bnx2i iSCSI driver.

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1211935729.18326.185.camel@dell>
Date:	Tue, 27 May 2008 17:48:49 -0700
From:	"Michael Chan" <mchan@...adcom.com>
To:	"David Miller" <davem@...emloft.net>
cc:	rdreier@...co.com, anilgv@...adcom.com, michaelc@...wisc.edu,
	netdev <netdev@...r.kernel.org>, linux-scsi@...r.kernel.org,
	open-iscsi@...glegroups.com
Subject: Re: [PATCH 3/3] bnx2i: Add bnx2i iSCSI driver.

On Tue, 2008-05-27 at 12:52 -0700, David Miller wrote:
> From: Roland Dreier <rdreier@...co.com>
> Date: Tue, 27 May 2008 07:38:19 -0700
> 
> > So you are creating sockets just to reserve TCP ports to avoid host
> > stack clashes with your offload engine?  Wasn't this approach strongly
> > rejected (in the context of iWARP) in the past?
> 
> Yes, it was, and likewise similar hacks in other areas will
> be rejected similarly.
> 

If we change the implementation to use a separate IP address and
separate MAC address for iSCSI, will it be acceptable?  The iSCSI IP/MAC
addresses will be unknown to the Linux TCP stack and so no sharing of
the 4-tuple space will be needed.

The patches will be very similar, except that all inet calls and
notifiers will be removed.



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html