Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 06 Jun 2006 18:47:06 -0700
From:      Nate Lawson <nate@root.org>
To:        Danny Braniss <danny@cs.huji.ac.il>
Cc:        Maxim Sobolev <sobomax@sippysoft.com>, scsi@freebsd.org
Subject:   Re: iSCSI target
Message-ID:  <4486301A.7080804@root.org>
In-Reply-To: <E1FnYnO-0008la-Cw@cs1.cs.huji.ac.il>
References:  <E1FnYnO-0008la-Cw@cs1.cs.huji.ac.il>

next in thread | previous in thread | raw e-mail | index | archive | help
Danny Braniss wrote:
> hi,
> 	the latest noise about iSCSI has pricked my curiosity.
> Since the iSCSI protocol part is almost ok,
> Q: How complicated can it be to write the cam-target, taking into
>    concideration that there is no hardware involved.
> 
> my idea is to have the non time critical stuff in userland (login, negotiation
> etc) and the rest inside the kernel.
>

The first task is just to support target mode in your iscsi driver.  To 
do that, you just have to support the ATIO, CTIO, INOT, etc. CCBs.  See 
isp, ahc, or now mpt for examples.  Once you have that done, the 
userland src/share/examples/scsi_target should just work.

We already have all the infrastructure done to support various targets. 
  All you need to do to add new target types is add a hook into 
scsi_target(4) [the kernel driver] to allow kernel processing of target 
requests.

-- 
Nate



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4486301A.7080804>