Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759222Ab0KPV0H (ORCPT ); Tue, 16 Nov 2010 16:26:07 -0500 Received: from mail-yx0-f174.google.com ([209.85.213.174]:58093 "EHLO mail-yx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757580Ab0KPV0F (ORCPT ); Tue, 16 Nov 2010 16:26:05 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=pjvfnmEIjpVZ2MWLH0AypUvHX7iYq2IGrhzphKX9Xha18B6yHkgXR6Qow4hnxskFvn G6BkSxKw9H8DzCkRti7KrLmwBPiCxph62n1xHh50dmGC+4oB3AVe1+c//72IUg4S5k1V 6JmP139Rp5bIo/V4DrIc6bFlKq4xbRvFvCpS0= MIME-Version: 1.0 In-Reply-To: References: <1289606118.3015.539.camel@mulgrave.site> <20101113051635.GA11613@havoc.gtf.org> <20101116071029.GA13540@havoc.gtf.org> Date: Tue, 16 Nov 2010 16:26:03 -0500 X-Google-Sender-Auth: c8ICXF98_q5hnrAhaXjScrwvDBk Message-ID: Subject: Re: [PATCH v5] SCSI host lock push-down From: Jeff Garzik To: Linus Torvalds Cc: James Bottomley , "Nicholas A. Bellinger" , Andrew Morton , linux-scsi , linux-kernel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 837 Lines: 20 On Tue, Nov 16, 2010 at 12:25 PM, Linus Torvalds wrote: > On Mon, Nov 15, 2010 at 11:10 PM, Jeff Garzik wrote: >> >> Move the mid-layer's ->queuecommand() invocation from being locked >> with the host lock to being unlocked to facilitate speeding up the >> critical path for drivers who don't need this lock taken anyway. > > Looks ok to me. How should I take this? Just as a patch? Or should it > go through the scsi tree? Directly as a single patch (v5), if James acks; otherwise through jejb/scsi-rc-fixes.git I would presume. 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/