From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Roland Dreier <rdreier@cisco.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Steve Wise <swise@opengridcomputing.com>,
davem@davemloft.net, Divy Le Ray <divy@chelsio.com>,
Karen Xie <kxie@chelsio.com>,
netdev@vger.kernel.org, open-iscsi@googlegroups.com,
michaelc@cs.wisc.edu, daisyc@us.ibm.com, wenxiong@us.ibm.com,
bhua@us.ibm.com, Dimitrios Michailidis <dm@chelsio.com>,
Casey Leedom <leedom@chelsio.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH 1/1] cxgb3i: cxgb3 iSCSI initiator
Date: Sun, 10 Aug 2008 10:19:35 +0100 [thread overview]
Message-ID: <20080810101935.5c8e8e9a@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <adazlnlzc60.fsf@cisco.com>
> - 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.
> system. But this means that to start with the HBA needs its own ARP,
> ICMP, routing, etc interface, which means we need some (probably new)
> interface to configure all of this. And then it doesn't work in lots
Its another system so surely SNMP ;)
More seriously I do think iSCSI is actually a subtly special case of TOE.
Most TOE disintegrates under carefully chosen "malicious" workloads
because of the way it is optimised, and the lack of security integration
ranges can be very very dangeorus. A pure iSCSI connection is generally
private, single purpose and really is the classic application of "pigs fly
given enough thrust" - which is the only way to make the pig in question
(iSCSI) work properly.
next prev parent reply other threads:[~2008-08-10 10:00 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200807300019.m6U0JkdY012558@localhost.localdomain>
2008-07-30 19:35 ` Jeff Garzik
2008-07-30 21:35 ` Roland Dreier
2008-08-01 0:51 ` Divy Le Ray
2008-08-07 18:45 ` Divy Le Ray
2008-08-07 20:07 ` Mike Christie
2008-08-08 18:09 ` Steve Wise
2008-08-08 22:15 ` Jeff Garzik
2008-08-08 22:20 ` Jeff Garzik
2008-08-09 7:28 ` David Miller
2008-08-09 14:04 ` Steve Wise
2008-08-10 5:14 ` Roland Dreier
2008-08-10 5:47 ` David Miller
2008-08-10 6:34 ` Herbert Xu
2008-08-10 17:57 ` Steve Wise
2008-08-11 16:09 ` Roland Dreier
2008-08-11 21:09 ` David Miller
2008-08-11 21:37 ` Roland Dreier
2008-08-11 21:51 ` David Miller
2008-08-11 23:20 ` Steve Wise
2008-08-11 23:45 ` Divy Le Ray
2008-08-12 0:22 ` David Miller
2008-08-10 5:12 ` Roland Dreier
2008-08-10 5:46 ` David Miller
2008-08-11 16:07 ` Roland Dreier
2008-08-11 21:08 ` David Miller
2008-08-11 21:39 ` Roland Dreier
2008-08-11 21:52 ` David Miller
2008-08-11 18:13 ` Rick Jones
2008-08-11 21:12 ` David Miller
2008-08-11 21:41 ` Roland Dreier
2008-08-11 21:53 ` David Miller
2008-08-12 21:57 ` Divy Le Ray
2008-08-12 22:01 ` David Miller
2008-08-12 22:02 ` David Miller
2008-08-12 22:21 ` Divy Le Ray
2008-08-13 1:57 ` Herbert Xu
2008-08-13 18:35 ` Vladislav Bolkhovitin
2008-08-13 19:29 ` Jeff Garzik
2008-08-13 20:13 ` David Miller
2008-08-14 18:24 ` Vladislav Bolkhovitin
2008-08-14 21:59 ` Nicholas A. Bellinger
2008-08-13 20:23 ` David Miller
2008-08-14 18:27 ` Vladislav Bolkhovitin
2008-08-14 18:30 ` Vladislav Bolkhovitin
2008-08-13 21:27 ` Roland Dreier
2008-08-13 22:08 ` David Miller
2008-08-13 23:03 ` Roland Dreier
2008-08-13 23:12 ` David Miller
2008-08-14 1:26 ` Tom Tucker
2008-08-14 1:37 ` David Miller
2008-08-14 1:52 ` Steve Wise
2008-08-14 2:05 ` David Miller
2008-08-14 2:44 ` Steve Wise
2008-08-14 1:57 ` Tom Tucker
2008-08-14 2:07 ` David Miller
2008-08-14 2:09 ` David Miller
2008-08-10 6:24 ` Herbert Xu
2008-08-10 9:19 ` Alan Cox [this message]
2008-08-10 12:49 ` Jeff Garzik
2008-08-10 14:54 ` James Bottomley
2008-08-11 16:50 ` Mike Christie
2008-07-31 1:24 ` Karen Xie
2008-07-31 12:45 ` Boaz Harrosh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080810101935.5c8e8e9a@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bhua@us.ibm.com \
--cc=daisyc@us.ibm.com \
--cc=davem@davemloft.net \
--cc=divy@chelsio.com \
--cc=dm@chelsio.com \
--cc=jgarzik@pobox.com \
--cc=kxie@chelsio.com \
--cc=leedom@chelsio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=netdev@vger.kernel.org \
--cc=open-iscsi@googlegroups.com \
--cc=rdreier@cisco.com \
--cc=swise@opengridcomputing.com \
--cc=wenxiong@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®