From: Mike Galbraith <efault@gmx.de>
To: balbir@linux.vnet.ibm.com
Cc: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
"Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: Make yield_task_fair more efficient
Date: Thu, 21 Feb 2008 13:02:34 +0100 [thread overview]
Message-ID: <1203595354.19641.5.camel@homer.simson.net> (raw)
In-Reply-To: <47BD44FF.7070104@linux.vnet.ibm.com>
Hi,
On Thu, 2008-02-21 at 15:01 +0530, Balbir Singh wrote:
> Ingo Molnar wrote:
> > * Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> >
> >> If you insist that sched_yield() is bad, I might agree, but how does
> >> my patch make things worse. [...]
> >
> > it puts new instructions into the hotpath.
> >
> >> [...] In my benchmarks, it has helped the sched_yield case, why is
> >> that bad? [...]
> >
> > I had the same cache for the rightmost task in earlier CFS (it's a
> > really obvious thing) but removed it. It wasnt a bad idea, but it hurt
> > the fastpath hence i removed it. Algorithms and implementations are a
> > constant balancing act.
>
> This is more convincing, was the code ever in git? How did you measure the
> overhead?
Counting enqueue/dequeue cycles on my 3GHz P4/HT running a 60 seconds
netperf test that does ~85k/s context switches shows:
sched_cycles: 7198444348 unpatched
vs
sched_cycles: 8574036268 patched
-Mike
diff --git a/include/linux/sched.h b/include/linux/sched.h
index e217d18..a71edfe 100644
--- a/include/linux/sched.h
+++ b/include/linux/sched.h
@@ -1262,6 +1262,7 @@ struct task_struct {
int latency_record_count;
struct latency_record latency_record[LT_SAVECOUNT];
#endif
+ unsigned long long sched_cycles;
};
/*
diff --git a/kernel/exit.c b/kernel/exit.c
index 506a957..c5c3d5e 100644
--- a/kernel/exit.c
+++ b/kernel/exit.c
@@ -174,6 +174,8 @@ repeat:
}
write_unlock_irq(&tasklist_lock);
+ if (!strcmp("netperf", p->comm) || !strcmp("netserver", p->comm))
+ printk(KERN_WARNING "%s:%d sched_cycles: %Ld\n", p->comm, p->pid, p->sched_cycles);
release_thread(p);
call_rcu(&p->rcu, delayed_put_task_struct);
diff --git a/kernel/sched.c b/kernel/sched.c
index f28f19e..d7c1b0b 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -1301,15 +1301,25 @@ static void set_load_weight(struct task_struct *p)
static void enqueue_task(struct rq *rq, struct task_struct *p, int wakeup)
{
+ unsigned long long then, now;
+
+ rdtscll(then);
sched_info_queued(p);
p->sched_class->enqueue_task(rq, p, wakeup);
p->se.on_rq = 1;
+ rdtscll(now);
+ p->sched_cycles += now - then;
}
static void dequeue_task(struct rq *rq, struct task_struct *p, int sleep)
{
+ unsigned long long then, now;
+
+ rdtscll(then);
p->sched_class->dequeue_task(rq, p, sleep);
p->se.on_rq = 0;
+ rdtscll(now);
+ p->sched_cycles += now - then;
}
/*
@@ -2009,6 +2019,7 @@ void wake_up_new_task(struct task_struct *p, unsigned long clone_flags)
update_rq_clock(rq);
p->prio = effective_prio(p);
+ p->sched_cycles = 0;
if (!p->sched_class->task_new || !current->se.on_rq) {
activate_task(rq, p, 0);
next prev parent reply other threads:[~2008-02-21 12:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 5:33 Balbir Singh
2008-02-21 6:04 ` Ingo Molnar
2008-02-21 6:51 ` Balbir Singh
2008-02-21 7:07 ` Ingo Molnar
2008-02-21 7:39 ` Balbir Singh
2008-02-21 8:43 ` Peter Zijlstra
2008-02-21 8:50 ` Balbir Singh
2008-02-21 9:04 ` Ingo Molnar
2008-02-21 9:31 ` Balbir Singh
2008-02-21 9:42 ` Ingo Molnar
2008-02-21 9:44 ` Balbir Singh
2008-02-21 9:43 ` Peter Zijlstra
2008-02-21 9:42 ` Balbir Singh
2008-02-21 10:01 ` Peter Zijlstra
2008-02-21 10:07 ` Balbir Singh
2008-02-21 11:12 ` Peter Zijlstra
2008-02-21 11:27 ` Balbir Singh
2008-02-21 20:38 ` Jens Axboe
2008-02-21 20:55 ` Jens Axboe
2008-02-22 3:27 ` Balbir Singh
2008-02-21 10:17 ` Balbir Singh
2008-02-21 12:02 ` Mike Galbraith [this message]
2008-02-21 12:06 ` Mike Galbraith
2008-02-21 13:29 ` Balbir Singh
2008-02-21 14:38 ` Jörn Engel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1203595354.19641.5.camel@homer.simson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=balbir@linux.vnet.ibm.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vatsa@linux.vnet.ibm.com \
--cc=yanmin_zhang@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome