[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1334153450.23924.243.camel@gandalf.stny.rr.com>
Date: Wed, 11 Apr 2012 10:10:50 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Hillf Danton <dhillf@...il.com>
Cc: Juri Lelli <juri.lelli@...il.com>, peterz@...radead.org,
tglx@...utronix.de, mingo@...hat.com, cfriesen@...tel.com,
oleg@...hat.com, fweisbec@...il.com, darren@...art.com,
johan.eker@...csson.com, p.faure@...tech.ch,
linux-kernel@...r.kernel.org, claudio@...dence.eu.com,
michael@...rulasolutions.com, fcheccon@...per.es
Subject: Re: [PATCH 06/16] sched: SCHED_DEADLINE push and pull logic
On Fri, 2012-04-06 at 21:39 +0800, Hillf Danton wrote:
> > +static void inc_dl_migration(struct sched_dl_entity *dl_se, struct dl_rq *dl_rq)
> > +{
> > + dl_rq = &rq_of_dl_rq(dl_rq)->dl;
> > +
> > + dl_rq->dl_nr_total++;
> > + if (dl_se->nr_cpus_allowed > 1)
> > + dl_rq->dl_nr_migratory++;
> > +
> > + update_dl_migration(dl_rq);
>
> if (dl_se->nr_cpus_allowed > 1) {
> dl_rq->dl_nr_migratory++;
> /* No change in migratory, no update of migration */
This is not true. As dl_nr_total changed. If there was only one dl task
queued that can migrate, and then another dl task is queued but this
task can not migrate, the update_dl_migration still needs to be called.
As dl_nr_migratory would be 1, but now dl_nr_total > 1. This means we
are now overloaded.
> update_dl_migration(dl_rq);
> }
>
> > +}
> > +
> > +static void dec_dl_migration(struct sched_dl_entity *dl_se, struct dl_rq *dl_rq)
> > +{
> > + dl_rq = &rq_of_dl_rq(dl_rq)->dl;
> > +
> > + dl_rq->dl_nr_total--;
> > + if (dl_se->nr_cpus_allowed > 1)
> > + dl_rq->dl_nr_migratory--;
> > +
> > + update_dl_migration(dl_rq);
>
> ditto
ditto.
>
> > +}
> > +
> > +/*
> > + * The list of pushable -deadline task is not a plist, like in
> > + * sched_rt.c, it is an rb-tree with tasks ordered by deadline.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists