Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 10 Nov 2002 15:45:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 10 Nov 2002 15:45:29 -0500 Received: from packet.digeo.com ([12.110.80.53]:51396 "EHLO packet.digeo.com") by vger.kernel.org with ESMTP id ; Sun, 10 Nov 2002 15:45:28 -0500 Message-ID: <3DCEC6F7.E5EC1147@digeo.com> Date: Sun, 10 Nov 2002 12:52:07 -0800 From: Andrew Morton X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.5.46 i686) X-Accept-Language: en MIME-Version: 1.0 To: Andrea Arcangeli CC: Rik van Riel , Con Kolivas , linux kernel mailing list , marcelo@conectiva.com.br Subject: Re: [BENCHMARK] 2.4.{18,19{-ck9},20rc1{-aa1}} with contest References: <20021110024451.GE2544@x30.random> <20021110201045.GA4056@x30.random> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 10 Nov 2002 20:52:08.0428 (UTC) FILETIME=[08B89AC0:01C288FB] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 867 Lines: 20 Andrea Arcangeli wrote: > > > Whether the IO is synchronous or asynchronous shouldn't matter much, > > the fact the I/O is sync or async makes the whole difference. with sync > reads the vmstat line in the read column will be always very small > compared to the write column under a write flood. This can be fixed either: > > 1) with hacks in the elevator ala read-latency that are not generic and > could decrease performance of other workloads read-latency will only do the front-insertion if it was unable to find a merge or insert on the tail-to-head search. And the problem it desparately addresses is severe. - 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/