From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261932AbUC0Xo0 (ORCPT ); Sat, 27 Mar 2004 18:44:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261931AbUC0Xo0 (ORCPT ); Sat, 27 Mar 2004 18:44:26 -0500 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:46260 "EHLO www.linux.org.uk") by vger.kernel.org with ESMTP id S261907AbUC0XoY (ORCPT ); Sat, 27 Mar 2004 18:44:24 -0500 Message-ID: <406611CA.3050804@pobox.com> Date: Sat, 27 Mar 2004 18:44:10 -0500 From: Jeff Garzik User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nick Piggin CC: linux-ide@vger.kernel.org, Linux Kernel , Andrew Morton Subject: Re: [PATCH] speed up SATA References: <4066021A.20308@pobox.com> <40661049.1050004@yahoo.com.au> In-Reply-To: <40661049.1050004@yahoo.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Nick Piggin wrote: > I think 32MB is too much. You incur latency and lose > scheduling grainularity. I bet returns start diminishing > pretty quickly after 1MB or so. See my reply to Bart. Also, it is not the driver's responsibility to do anything but export the hardware maximums. It's up to the sysadmin to choose a disk scheduling policy they like, which implies that a _scheduler_, not each individual driver, should place policy limitations on max_sectors. Jeff