From owner-freebsd-cluster@FreeBSD.ORG  Mon Jun 23 12:17:16 2003
Return-Path: <owner-freebsd-cluster@FreeBSD.ORG>
Delivered-To: freebsd-cluster@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A318137B401
	for <freebsd-cluster@freebsd.org>;
	Mon, 23 Jun 2003 12:17:16 -0700 (PDT)
Received: from walnut.he.net (walnut.he.net [64.71.137.114])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2BD1343FEC
	for <freebsd-cluster@freebsd.org>;
	Mon, 23 Jun 2003 12:17:16 -0700 (PDT)
	(envelope-from kmacy@fsmware.com)
Received: from localhost (kmacy@localhost) by walnut.he.net
	(8.8.6p2003-03-31/8.8.2) with ESMTP id MAA09446; Mon, 23 Jun 2003 12:17:05
	-0700
Date: Mon, 23 Jun 2003 12:17:05 -0700 (PDT)
From: Kip Macy <kmacy@fsmware.com>
X-Sender: kmacy@walnut.he.net
To: Peter Ross <Peter.Ross@alumni.tu-berlin.de>
In-Reply-To: <20030623214253.O520@guckloch.zuhause>
Message-ID: <Pine.LNX.4.21.0306231214400.31872-100000@walnut.he.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-cluster@freebsd.org
Subject: Re: Re[2]: iSCSI and clustering with FreeBSD
X-BeenThere: freebsd-cluster@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Clustering FreeBSD <freebsd-cluster.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-cluster>,
	<mailto:freebsd-cluster-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-cluster>
List-Post: <mailto:freebsd-cluster@freebsd.org>
List-Help: <mailto:freebsd-cluster-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-cluster>,
	<mailto:freebsd-cluster-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2003 19:17:16 -0000

> It starts with basic design questions. Sorry, I am always late..
> 
> I want to implement the iSCSI initiator as a CAM SIM driver. I was pointed
> to the umass driver which is a "translator" between SCSI and USB commands.
> The developers handbook gives me a good introduction how to write a SIM
> driver.

A good place to start is to write something strictly in userland that logs
in and generates traffic to the target. When I wrote my target it was
initially all in userland. After, the protocol handling had proven to be 
robust I moved it into the kernel.

If you try to familiarize yourself with too many things at once, it may
take you a long time to get started.


				-Kip