Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932776AbWLSKnU (ORCPT ); Tue, 19 Dec 2006 05:43:20 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932775AbWLSKnU (ORCPT ); Tue, 19 Dec 2006 05:43:20 -0500 Received: from a222036.upc-a.chello.nl ([62.163.222.36]:38966 "EHLO laptopd505.fenrus.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S932776AbWLSKnT (ORCPT ); Tue, 19 Dec 2006 05:43:19 -0500 X-Greylist: delayed 2370 seconds by postgrey-1.27 at vger.kernel.org; Tue, 19 Dec 2006 05:43:18 EST Subject: Re: [PATCH] scsi_execute_async() should add to the tail of the queue From: Arjan van de Ven To: Dan Aloni Cc: Linux Kernel List , linux-scsi@vger.kernel.org, Mike Christie In-Reply-To: <20061219083507.GA20847@localdomain> References: <20061219083507.GA20847@localdomain> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 19 Dec 2006 11:03:33 +0100 Message-Id: <1166522613.3365.1198.camel@laptopd505.fenrus.org> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2.1 (2.8.2.1-2.fc6) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 977 Lines: 25 On Tue, 2006-12-19 at 10:35 +0200, Dan Aloni wrote: > Hello, > > scsi_execute_async() has replaced scsi_do_req() a few versions ago, > but it also incurred a change of behavior. I noticed that over-queuing > a SCSI device using that function causes I/Os to be starved from > low-level queuing for no justified reason. > > I think it makes much more sense to perserve the original behaviour > of scsi_do_req() and add the request to the tail of the queue. Hi, some things should really be added to the head of the queue, like maintenance requests and error handling requests. Are you sure this is the right change? At least I'd expect 2 apis, one for a head and one for a "normal" queueing... Greetings, Arjan van de Ven - 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/