From owner-freebsd-scsi@FreeBSD.ORG  Fri Feb 18 20:36:59 2005
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id E1EFD16A4CE; Fri, 18 Feb 2005 20:36:59 +0000 (GMT)
Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 617D543D53; Fri, 18 Feb 2005 20:36:59 +0000 (GMT)
	(envelope-from danny@cs.huji.ac.il)
Received: from pampa.cs.huji.ac.il ([132.65.80.32])
	by cs1.cs.huji.ac.il with esmtp
	id 1D2Erx-000HSG-CK; Fri, 18 Feb 2005 22:36:57 +0200
X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4
To: Scott Long <scottl@freebsd.org>
In-Reply-To: Message from Scott Long <scottl@freebsd.org> 
	<20050218094946.I24964@pooker.samsco.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 18 Feb 2005 22:36:56 +0200
From: Danny Braniss <danny@cs.huji.ac.il>
Message-ID: <E1D2Erx-000HSG-CK@cs1.cs.huji.ac.il>
cc: scsi@freebsd.org
Subject: Re: iSCSI first steps! 
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2005 20:37:00 -0000

> On Fri, 18 Feb 2005, Danny Braniss wrote:
> 
> Looks wonderful!  What are your next steps for it?
> 
writing, of course :-), i mean scsi write, which, if i don't get stone
walled, should be very soon (i was stuck for almost a week trying
to figure out 'redirect connection' and NOP_IN/NOP_OUT).

major things that need to be done:
	- real parameter negotiation - just coding, not much technology
	  involved.
	- same with authentication
	- error recovery, a real PITA.
i still have to do some experimentation with the CAM (and learn some)
	- the RESCAN should be triggered after the target is 'locacated', im
using 'camcontrol rescan' at the moment because i still can't figure that
one.
	- same when the connection is closed/dropped.
i have three target to try it against, after that will probably need
other candidates ...

	- task management, async events. (part of the RFC).

and allot of fine tunning.

danny