linux-kernel - Re: [tip:tracing/ftrace] tracing: implement trace_clock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090226175758.GA8262@elte.hu>
Date:	Thu, 26 Feb 2009 18:57:58 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	hpa@...or.com, mingo@...hat.com, rostedt@...dmis.org,
	peterz@...radead.org, tglx@...utronix.de,
	linux-kernel@...r.kernel.org, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:tracing/ftrace] tracing: implement trace_clock_*() APIs


* Frederic Weisbecker <fweisbec@...il.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
--
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/