Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 7 Dec 2002 01:12:42 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 7 Dec 2002 01:12:42 -0500 Received: from adsl-67-64-81-217.dsl.austtx.swbell.net ([67.64.81.217]:48769 "HELO digitalroadkill.net") by vger.kernel.org with SMTP id ; Sat, 7 Dec 2002 01:12:41 -0500 Subject: Re: [BENCHMARK] max bomb segment tuning with read latency 2 patch in contest From: GrandMasterLee To: Andrew Morton Cc: Con Kolivas , linux kernel mailing list In-Reply-To: <3DF18D38.F493636C@digeo.com> References: <200212071620.05503.conman@kolivas.net> <3DF18D38.F493636C@digeo.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Digitalroadkill.net Message-Id: <1039242017.2855.26.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 07 Dec 2002 00:20:17 -0600 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1386 Lines: 40 On Fri, 2002-12-06 at 23:55, Andrew Morton wrote: [...] > If the SMP machine is using scsi then that tends to make the elevator > changes less effective. Because the disk sort-of has its own internal > elevator which in my testing on a Fujitsu disk has the same ill-advised > design as the kernel's elevator: it treats reads and writes in a similar > manner. > > Setting the tag depth to zero helps heaps. > > But as you're interested in `desktop responsiveness' you should be > mostly testing against IDE disks. Their behavour tends to be quite > different. One interesting thing about my current setup, with all scsi or FC disks, is that bomb never displays > 0. Example: elvtune /dev/sdn yields: /dev/sdn elevator ID 17 read_latency: 8192 write_latency: 16384 max_bomb_segments: 0 elvtune -b 6 /dev/sdn yields: /dev/sdn elevator ID 17 read_latency: 8192 write_latency: 16384 max_bomb_segments: 0 Is it because I just do volume management at the hardware level and use whole disks? Or is that something else? - 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/