From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [PATCH] speed up SATA Date: Sat, 27 Mar 2004 18:44:10 -0500 Sender: linux-ide-owner@vger.kernel.org Message-ID: <406611CA.3050804@pobox.com> References: <4066021A.20308@pobox.com> <40661049.1050004@yahoo.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: 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 In-Reply-To: <40661049.1050004@yahoo.com.au> List-Id: linux-ide@vger.kernel.org To: Nick Piggin Cc: linux-ide@vger.kernel.org, Linux Kernel , Andrew Morton 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