Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757608Ab1EMWRB (ORCPT ); Fri, 13 May 2011 18:17:01 -0400 Received: from gate.crashing.org ([63.228.1.57]:55232 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751401Ab1EMWRA (ORCPT ); Fri, 13 May 2011 18:17:00 -0400 Subject: Re: [GIT PULL] isci merge candidate From: Benjamin Herrenschmidt To: Dan Williams Cc: Linus Torvalds , "James.Bottomley@hansenpartnership.com" , Christoph Hellwig , linux-kernel , linux-scsi , "Jiang, Dave" , David Milburn , "Ciechanowski, Ed" , "Nadolski, Edmund" , "Danecki, Jacek" , "Skirvin, Jeffrey D" , Jeff Garzik In-Reply-To: <4DCDA663.2040202@intel.com> References: <1305317680.21099.83.camel@dwillia2-linux> <4DCDA663.2040202@intel.com> Content-Type: text/plain; charset="UTF-8" Date: Sat, 14 May 2011 08:16:02 +1000 Message-ID: <1305324962.2781.5.camel@pasglop> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 906 Lines: 21 > It's a SAS (serial-attached-scsi) driver so it ties in to libsas rather > than libata (libsas itself ties in to libata for tunnelling SATA > protocol over SAS). The size is attributable to the fact that all > protocol handling for non-fast path i/o is handled by software. There > are still cleanups that can be made, but likely not on the on the same > order of what we have already done. How much of that non-fast-path could/should be in generic code vs. in the driver specific code ? IE. If somebody comes up with another "dumb" SAS adapter tomorrow that doesn't do all that magic in an offload CPU, is any of that code re-usable ? Cheers, Ben. -- 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/