Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965253AbVI1CHZ (ORCPT ); Tue, 27 Sep 2005 22:07:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965250AbVI1CHZ (ORCPT ); Tue, 27 Sep 2005 22:07:25 -0400 Received: from mail.dvmed.net ([216.237.124.58]:28126 "EHLO mail.dvmed.net") by vger.kernel.org with ESMTP id S965249AbVI1CHY (ORCPT ); Tue, 27 Sep 2005 22:07:24 -0400 Message-ID: <4339FACB.2090606@pobox.com> Date: Tue, 27 Sep 2005 22:07:07 -0400 From: Jeff Garzik User-Agent: Mozilla Thunderbird 1.0.6-1.1.fc4 (X11/20050720) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Luben Tuikov CC: James Bottomley , Christoph Hellwig , Linus Torvalds , Andrew Morton , Linux Kernel Mailing List , SCSI Mailing List Subject: Re: I request inclusion of SAS Transport Layer and AIC-94xx into the kernel References: <4339440C.6090107@adaptec.com> <20050927131959.GA30329@infradead.org> <43395ED0.6070504@adaptec.com> <1127836380.4814.36.camel@mulgrave> <43399F17.4090004@adaptec.com> <4339ACDA.3090801@pobox.com> <4339BD58.7060300@adaptec.com> <4339C12C.5020004@pobox.com> <4339CFC7.6080507@adaptec.com> In-Reply-To: <4339CFC7.6080507@adaptec.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1938 Lines: 55 Luben Tuikov wrote: > On 09/27/05 18:01, Jeff Garzik wrote: >>Just follow the recipe Christoph outlined. It's not difficult, just >>requires some work. > > > Anyone have a clear technical plan and/or infrastructure > on how to do this? Any specs, plans, consolidations, etc? Yes, read Christoph's todo list. We need to separate out bits specific to parallel SCSI, moving the bits to transport-specific code, since SAS doesn't need them. >>It does an end run around 90% of the SCSI core. You might as well make >>it a block driver, if you're going to do that. > > > The "90%" part isn't quite true. > > But going with a block device isn't that bad: > Now since the architecture _is_ SCSI after all, what would be > needed is a minimal, fast, straightforward, SAM/SPC fully complient > new SCSI Core. That SCSI Core would register block devices > with the block layer. Maybe Jens can point out cool things > to do and make the whole infrastructure fast and very fast. > (since we don't need to be bound by this legacy stuff) > > Essentially other new technology LLDD and Transport layers > can probably make use of this: Infiniband, USB2 Storage, etc. > > So if all you have is an AIC-94xx or BCM8603 storage chip > you can exclule all of the legacy SCSI Core and compile this > new mean, lean, fast SAM Core. > > Jeff, this isn't bad at all! > > Are you willing to contribute to such an effort? No. I'm much more willing to help integrate aic94xx and Broadcom/ServerWorks into the existing SCSI core, working with the community. As Andrew guessed, it's a way to get you your own playpen, where you won't be constrained by members of the Linux-SCSI community. Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/