Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756890Ab0BRKTX (ORCPT ); Thu, 18 Feb 2010 05:19:23 -0500 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:41566 "EHLO www.etchedpixels.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753938Ab0BRKTU (ORCPT ); Thu, 18 Feb 2010 05:19:20 -0500 Date: Thu, 18 Feb 2010 10:16:03 +0000 From: Alan Cox To: Mark Lord Cc: Alan Cox , jeff@garzik.org.com, linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org Subject: Re: [RFC 1/4] libata: cache device select Message-ID: <20100218101603.23c16786@lxorguk.ukuu.org.uk> In-Reply-To: <4B7CCC7E.3060108@teksavvy.com> References: <20100217130847.16338.55586.stgit@localhost.localdomain> <4B7CCC7E.3060108@teksavvy.com> X-Mailer: Claws Mail 3.7.4 (GTK+ 2.18.6; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 862 Lines: 19 O> I totally agree with this patch, but question the timings used to justify it. > Surely the overhead is only 1-2usec for the case where the device > is the one that was already selected (on a "smart" interface) ? IFF you have a smart interface. A lot of the controllers in the PCI space don't appear to be that clever. > And for the case where the currently selected device is different > than the desired device (the 1msec case), this patch makes little/no difference? Correct, but even with two devices per cable (which is not the most common setup) you win. Worst case (which I've never seen) you draw. Alan -- 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/