Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 27 Oct 2001 09:28:02 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 27 Oct 2001 09:27:50 -0400 Received: from smtp2.libero.it ([193.70.192.52]:14302 "EHLO smtp2.libero.it") by vger.kernel.org with ESMTP id ; Sat, 27 Oct 2001 09:27:40 -0400 Message-ID: <3BDAB344.CE25D5D@denise.shiny.it> Date: Sat, 27 Oct 2001 15:14:44 +0200 From: Giuliano Pochini X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.4.13-pre1 ppc) X-Accept-Language: en MIME-Version: 1.0 To: zlatko.calusic@iskon.hr CC: Linus Torvalds , Marcelo Tosatti , linux-mm@kvack.org, lkml Subject: Re: xmm2 - monitor Linux MM active/inactive lists graphically In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > block: 1024 slots per queue, batch=341 > > Wrote 600.00 MB in 71 seconds -> 8.39 MB/s (7.5 %CPU) > > Still very spiky, and during the write disk is uncapable of doing any > reads. IOW, no serious application can be started before writing has > finished. Shouldn't we favour reads over writes? Or is it just that > the elevator is not doing its job right, so reads suffer? > > procs memory swap io system cpu > r b w swpd free buff cache si so bi bo in cs us sy id > 0 1 1 0 3596 424 453416 0 0 0 40468 189 508 2 2 96 341*127K = ~40M. Batch is too high. It doesn't explain why reads get delayed so much, anyway. Bye. - 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/