[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <489EE3DC.9060202@pobox.com>
Date: Sun, 10 Aug 2008 08:49:32 -0400
From: Jeff Garzik <jgarzik@...ox.com>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
CC: Roland Dreier <rdreier@...co.com>,
Steve Wise <swise@...ngridcomputing.com>, davem@...emloft.net,
Divy Le Ray <divy@...lsio.com>, Karen Xie <kxie@...lsio.com>,
netdev@...r.kernel.org, open-iscsi@...glegroups.com,
michaelc@...wisc.edu, daisyc@...ibm.com, wenxiong@...ibm.com,
bhua@...ibm.com, Dimitrios Michailidis <dm@...lsio.com>,
Casey Leedom <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
Alan Cox wrote:
>> - It doesn't work in theory, because the suggestion (I guess) is that
>> the iSCSI HBA has its own MAC and IP and behaves like a separate
>
> The iSCSI HBA is its own system - that is the root of the problem.
Indeed.
Just like with TOE, from the net stack's point of view, an iSCSI HBA is
essentially a wholly asynchronous remote system [with a really fast
communication bus like PCI Express].
As such, the task becomes updating the net stack such that
formerly-private resources are now shared with an independent, external
system... with all the complexity, additional failure modes, and
additional security complications that come along with that.
Jeff
--
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