Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753624AbYHJKA4 (ORCPT ); Sun, 10 Aug 2008 06:00:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752500AbYHJKAq (ORCPT ); Sun, 10 Aug 2008 06:00:46 -0400 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:49053 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752267AbYHJKAo (ORCPT ); Sun, 10 Aug 2008 06:00:44 -0400 Date: Sun, 10 Aug 2008 10:19:35 +0100 From: Alan Cox To: Roland Dreier Cc: Jeff Garzik , Steve Wise , davem@davemloft.net, Divy Le Ray , Karen Xie , 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 , Casey Leedom , linux-scsi , LKML Subject: Re: [RFC][PATCH 1/1] cxgb3i: cxgb3 iSCSI initiator Message-ID: <20080810101935.5c8e8e9a@lxorguk.ukuu.org.uk> In-Reply-To: References: <200807300019.m6U0JkdY012558@localhost.localdomain> <200807311752.00911.divy@chelsio.com> <200808071145.03848.divy@chelsio.com> <489C8BEB.8060001@opengridcomputing.com> <489CC58D.4010606@pobox.com> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; x86_64-redhat-linux-gnu) Organization: Red Hat UK Cyf., Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, Y Deyrnas Gyfunol. Cofrestrwyd yng Nghymru a Lloegr o'r rhif cofrestru 3798903 Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1184 Lines: 28 > - 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/