[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aday73jxdfs.fsf@cisco.com>
Date: Wed, 30 Jul 2008 14:35:51 -0700
From: Roland Dreier <rdreier@...co.com>
To: Jeff Garzik <jgarzik@...ox.com>
Cc: Karen Xie <kxie@...lsio.com>, netdev@...r.kernel.org,
open-iscsi@...glegroups.com, davem@...emloft.net,
michaelc@...wisc.edu, swise@...ngridcomputing.com,
daisyc@...ibm.com, wenxiong@...ibm.com, bhua@...ibm.com,
divy@...lsio.com, dm@...lsio.com, leedom@...lsio.com,
linux-scsi <linux-scsi@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC][PATCH 1/1] cxgb3i: cxgb3 iSCSI initiator
> * From a networking standpoint, our main concern becomes how this
> interacts with the networking stack. In particular, I'm concerned
> based on reading the source that this driver uses "TCP port stealing"
> rather than using a totally separate MAC address (and IP).
>
> Stealing a TCP port on an IP/interface already assigned is a common
> solution in this space, but also a flawed one. Precisely because the
> kernel and applications are unaware of this "special, magic TCP port"
> you open the potential for application problems that are very
> difficult for an admin to diagnose based on observed behavior.
That's true, but using a separate MAC and IP opens up a bunch of other
operational problems. I don't think the right answer for iSCSI offload
is clear yet.
- R.
--
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
Powered by blists - more mailing lists