Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751477AbWCRFsu (ORCPT ); Sat, 18 Mar 2006 00:48:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751882AbWCRFsu (ORCPT ); Sat, 18 Mar 2006 00:48:50 -0500 Received: from mail.gmx.de ([213.165.64.20]:37547 "HELO mail.gmx.net") by vger.kernel.org with SMTP id S1751477AbWCRFst (ORCPT ); Sat, 18 Mar 2006 00:48:49 -0500 X-Authenticated: #14349625 Subject: Re: [2.6.16-rc6 patch] fix interactive task starvation From: Mike Galbraith To: Andrew Morton Cc: linux-kernel@vger.kernel.org, mingo@elte.hu In-Reply-To: <20060317211529.26969a16.akpm@osdl.org> References: <1142658480.8262.38.camel@homer> <20060317211529.26969a16.akpm@osdl.org> Content-Type: text/plain Date: Sat, 18 Mar 2006 06:50:30 +0100 Message-Id: <1142661030.8937.7.camel@homer> Mime-Version: 1.0 X-Mailer: Evolution 2.4.0 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3251 Lines: 97 On Fri, 2006-03-17 at 21:15 -0800, Andrew Morton wrote: > Mike Galbraith wrote: > > > > +#define EXPIRED_STARVING(rq) \ > > + ((STARVATION_LIMIT && ((rq)->expired_timestamp && \ > > + (jiffies - (rq)->expired_timestamp >= \ > > + STARVATION_LIMIT * ((rq)->nr_running) + 1))) || \ > > + ((rq)->curr->static_prio > (rq)->best_expired_prio)) > > Does this have to be a macro? > I suppose not, now inlined. -Mike Signed-off-by: Mike Galbraith --- linux-2.6.16-rc6/kernel/sched.c.org 2006-03-17 14:48:35.000000000 +0100 +++ linux-2.6.16-rc6/kernel/sched.c 2006-03-18 06:43:59.000000000 +0100 @@ -662,11 +662,36 @@ } /* + * We place interactive tasks back into the active array, if possible. + * + * To guarantee that this does not starve expired tasks we ignore the + * interactivity of a task if the first expired task had to wait more + * than a 'reasonable' amount of time. This deadline timeout is + * load-dependent, as the frequency of array switched decreases with + * increasing number of running tasks. We also ignore the interactivity + * if a better static_prio task has expired: + */ +static inline int expired_starving(runqueue_t *rq) +{ + int limit = STARVATION_LIMIT * rq->nr_running, starving; + + if (!limit || !rq->expired_timestamp) + return 0; + starving = jiffies - rq->expired_timestamp >= limit; + starving += rq->curr->static_prio > rq->best_expired_prio; + + return starving; +} + +/* * __activate_task - move a task to the runqueue. */ static inline void __activate_task(task_t *p, runqueue_t *rq) { - enqueue_task(p, rq->active); + prio_array_t *array = rq->active; + if (unlikely(expired_starving(rq))) + array = rq->expired; + enqueue_task(p, array); rq->nr_running++; } @@ -2461,22 +2486,6 @@ } /* - * We place interactive tasks back into the active array, if possible. - * - * To guarantee that this does not starve expired tasks we ignore the - * interactivity of a task if the first expired task had to wait more - * than a 'reasonable' amount of time. This deadline timeout is - * load-dependent, as the frequency of array switched decreases with - * increasing number of running tasks. We also ignore the interactivity - * if a better static_prio task has expired: - */ -#define EXPIRED_STARVING(rq) \ - ((STARVATION_LIMIT && ((rq)->expired_timestamp && \ - (jiffies - (rq)->expired_timestamp >= \ - STARVATION_LIMIT * ((rq)->nr_running) + 1))) || \ - ((rq)->curr->static_prio > (rq)->best_expired_prio)) - -/* * Account user cpu time to a process. * @p: the process that the cpu time gets accounted to * @hardirq_offset: the offset to subtract from hardirq_count() @@ -2611,7 +2620,7 @@ if (!rq->expired_timestamp) rq->expired_timestamp = jiffies; - if (!TASK_INTERACTIVE(p) || EXPIRED_STARVING(rq)) { + if (!TASK_INTERACTIVE(p) || expired_starving(rq)) { enqueue_task(p, rq->expired); if (p->static_prio < rq->best_expired_prio) rq->best_expired_prio = p->static_prio; - 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/