From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: hpa@zytor.com, mingo@redhat.com, rostedt@goodmis.org,
peterz@infradead.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:tracing/ftrace] tracing: implement trace_clock_*() APIs
Date: Thu, 26 Feb 2009 18:57:58 +0100 [thread overview]
Message-ID: <20090226175758.GA8262@elte.hu> (raw)
In-Reply-To: <20090226175302.GD5889@nowhere>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> I missed this one.
because i just posted it :)
> Wouldn't your previous idea of a cmpxchg global clock be
> better? Perhaps it would scale better while tracing on many
> cpus.
a cmpxchg global clock has exactly the same cacheline-bouncing
properties as the lock here, so there's no real difference.
Ingo
prev parent reply other threads:[~2009-02-26 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-14131f2f98ac350ee9e73faed916d2238a8b6a0d@kernel.org>
2009-02-26 17:53 ` [tip:tracing/ftrace] tracing: implement trace_clock_*() APIs Frederic Weisbecker
2009-02-26 17:57 ` Ingo Molnar [this message]
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=20090226175758.GA8262@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--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