From owner-freebsd-arch@FreeBSD.ORG Thu Sep 23 21:20:14 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BCD0216A4CE; Thu, 23 Sep 2004 21:20:14 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6522243D31; Thu, 23 Sep 2004 21:20:14 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id BB9367A403; Thu, 23 Sep 2004 14:20:13 -0700 (PDT) Message-ID: <41533E0D.9000908@elischer.org> Date: Thu, 23 Sep 2004 14:20:13 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Sam References: <41508FEB.6030203@elischer.org><20040923191423.GE61631@FreeBSD.org> <41532FA0.6030405@elischer.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: re@freebsd.org cc: freebsd-arch@freebsd.org Subject: Re: AoE for 4.x X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2004 21:20:14 -0000 you could look at the sbp driver that is part of the firewire code.. I think that may be the closest analog. Sam wrote: > On Thu, 23 Sep 2004, Julian Elischer wrote: > >> I think that if you have a working driver we can assign you a number. >> I do have some questions however.. >> >> this is AoE.. is it not possible at all to combne it with either the CAM >> framework (such as the atapicam stuff) or the existing ATA stuff.. >> Don't take this the wrong way.. it's just a question.. >> CAM is being used to talk to drives over firewire, usb, ata, scsi, >> fibrechannel. >> it would seem that to unify this would be something that we should >> look at.. >> Of course CAM itslef is showing its age in soem places and it could >> do with some work itself.. > > > It might be possible to plug into the CAM; I only briefly > glanced at it and it didn't appear appropriate. The ATA > layer definitely isn't as parts of ATA don't make sense > in this context (Read DMA, Read Multiple, eg) and AoE > devices don't conform to the simple hardware probe/attach > methodology (as I understand it). > > I would love to be proved wrong. I'm always willing to > try a new approach if it's demonstrably better. > > Sam