From owner-freebsd-scsi@FreeBSD.ORG Sun Oct 29 06:33:12 2006 Return-Path: X-Original-To: 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 64E7016A407 for ; Sun, 29 Oct 2006 06:33:12 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC73543D67 for ; Sun, 29 Oct 2006 06:33:11 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k9T6Wqqb026015; Sun, 29 Oct 2006 00:32:57 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <45444B14.8000102@samsco.org> Date: Sun, 29 Oct 2006 00:32:52 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5 MIME-Version: 1.0 To: Matthew Jacob References: <7579f7fb0610281836t4f13efcfm15c1b238cff96a7@mail.gmail.com> <7579f7fb0610281840j2ee74f5av18239d4c9c702460@mail.gmail.com> In-Reply-To: <7579f7fb0610281840j2ee74f5av18239d4c9c702460@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org Subject: Re: CAM_NEW_TRAN X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Oct 2006 06:33:12 -0000 Matthew Jacob wrote: >> >> iSCSI: >> I don't know - I haven't played with your iSCSI driver yet. I would >> actually expect things to be substantially easier as you can then make >> iSCSI a transport protocol and do transport specific things within it >> which are awkward otherwise. > > > Incomplete thought: to a first approximation it shouldn't really > affect you much at all. Most of the 'driver' changes are things just > put into slightly different structures and called something a bit > different. > > The notion then would be to start taking this further and doing more > and more useful things with it. > > For example, camlib/camcontrol would then be taught about the > different transport types and could report WWPNs and whatnot for FC > and whatever that ridiculous 511 byte UUID there is for iSCSI. > Everyone I know who uses FreeBSD with Fibre Channel and target mode > has to hack things to get that information. Making changes that forces application changes (xmcd, cdparanoia) is going to be hard to swallow. If they just need a recompile, that's a lot better. Having a shim for binary compatibility would be the best. All depends on how much work you want to put into it. Scott