From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Oleg Nesterov <oleg@redhat.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [RFC PATCH] posix-cpu-timers: optimize calling thread_group_cputime()
Date: Fri, 12 Jun 2009 13:20:08 +0200 [thread overview]
Message-ID: <20090612132008.0c6f3e93@dhcp-lab-109.englab.brq.redhat.com> (raw)
In-Reply-To: <1244804986.6691.1224.camel@laptop>
On Fri, 12 Jun 2009 13:09:46 +0200
Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> On Fri, 2009-06-12 at 12:39 +0200, Stanislaw Gruszka wrote:
> > - times->utime = cputime_add(times->utime, t->utime);
> > - times->stime = cputime_add(times->stime, t->stime);
> > - times->sum_exec_runtime += t->se.sum_exec_runtime;
> > + if (mask & TG_CPUCLOCK_UTIME)
> > + times->utime = cputime_add(times->utime, t->utime);
> > + if (mask & TG_CPUCLOCK_STIME)
> > + times->stime = cputime_add(times->stime, t->stime);
> > + if (mask & TG_CPUCLOCK_SCHED)
> > + times->sum_exec_runtime += t->se.sum_exec_runtime;
>
> Does adding 3 branches really make it faster?
Actually I did not any benchmarking yet, so I don't know what is the real
impact of the patch. I hope it make things taster but the result can be
opposite from my expectations.
> Since you're bound to want
> at least one, I would expect the cacheline to be hot (assuming all three
> variables live in the same cacheline -- if not, they should be!), so all
> you're avoiding is the addition.
utime, stime are probable in the same cache line, se.sum_exec_runtime is far away
from them in struct task_struct so it's in rather separate cache line.
Stanislaw
next prev parent reply other threads:[~2009-06-12 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 10:39 Stanislaw Gruszka
2009-06-12 11:09 ` Peter Zijlstra
2009-06-12 11:20 ` Stanislaw Gruszka [this message]
2009-06-12 14:25 ` Oleg Nesterov
2009-06-15 8:55 ` Stanislaw Gruszka
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=20090612132008.0c6f3e93@dhcp-lab-109.englab.brq.redhat.com \
--to=sgruszka@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®