Date: Wed, 30 Jul 2003 21:28:32 +0200
From: aradorlinux@yahoo.es
To: Con Kolivas <kernel@kolivas.org>
Cc: miller@techsource.com, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] O10int for interactivity
Message-Id: <20030730212832.22e065ad.aradorlinux@yahoo.es>
In-Reply-To: <200307301136.06396.kernel@kolivas.org>
References: <200307280112.16043.kernel@kolivas.org>
	<200307300035.01354.kernel@kolivas.org>
	<20030730031616.3ed14362.diegocg@teleline.es>
	<200307301136.06396.kernel@kolivas.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1118
Lines: 26

[changing email address; several hosts block mail from *@teleline/terra.es;
which is good if they're fighting against spam]
El Wed, 30 Jul 2003 11:36:06 +1000 Con Kolivas <kernel@kolivas.org> escribi?:

> The logic is in the difference between the dynamic and the static priority to 
> determine if a task is interactive. 
> current->static_prio - current->prio
> will give you a number of -5 to +5, with +5 being a good bonus and vice versa.
> however you need to ensure that the value you are fiddling with in the i/o 
> scheduler is actually due to the current process[1]

I think current really is the process submitting the request; at least in the
same function we've this:

        if (rq_data_dir(arq->request) == READ
                        || current->flags&PF_SYNCWRITE)

Which would be wrong if current isn't the process submitting the request.


Diego Calleja
-
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/