Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 11 Nov 2001 17:23:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 11 Nov 2001 17:23:04 -0500 Received: from [208.129.208.52] ([208.129.208.52]:53508 "EHLO xmailserver.org") by vger.kernel.org with ESMTP id ; Sun, 11 Nov 2001 17:22:51 -0500 Date: Sun, 11 Nov 2001 14:31:28 -0800 (PST) From: Davide Libenzi X-X-Sender: davide@blue1.dev.mcafeelabs.com To: Ingo Molnar cc: Mike Fedyk , Linus Torvalds , lkml , Alan Cox Subject: Re: [patch] scheduler cache affinity improvement for 2.4 kernels In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 11 Nov 2001, Davide Libenzi wrote: > Ingo, i'm giving the timer_ticks patch a try in my proposed scheduler coz > i like the idea of skipping the if inside goodness(), and i can do this > safely because inside the proposed scheduler i don't have any cross CPU > goodnesses ( no "if (p->processor != this_cpu) weight -= p->timer_ticks;" ). > I made a change to it anyway, that is adding a water-mark in the decay > behavior ( timer.c ). > When counter is above this watermark ( currently 20 ) the counter decay as > usual while if counter <= watermark, ticks accumulates in timer_ticks. > This solution keeps the same good behavior for CPU bound tasks while it > gives a "human"/current decay to tasks that has got a lot of counter > accumulation inside the recalc loop ( I/O bound ). The watermark is 10 ( DEF_COUNTER ) not 20. - Davide - 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/