From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Pierre-Marc Fournier <pierre-marc.fournier@polymtl.ca>,
Ingo Molnar <mingo@elte.hu>, GeunSik Lim <leemgs1@gmail.com>,
Zhaolei <zhaolei@cn.fujitsu.com>,
Wu Fengguang <fengguang.wu@intel.com>,
Jesper Juhl <jj@chaosbits.net>, Adrian Bunk <bunk@stusta.de>,
Harvey Harrison <harvey.harrison@gmail.com>,
"Robert P. J. Day" <rpjday@mindspring.com>,
Jaswinder Singh Rajput <jaswinderrajput@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
linux-kernel@vger.kernel.org,
Dominique Toupin <dominique.toupin@ericsson.com>,
Michel Dagenais <michel.dagenais@polymtl.ca>
Subject: Re: Relicensing tracepoints and markers to Dual LGPL v2.1/GPL v2,headers to Dual BSD/GPL
Date: Mon, 26 Oct 2009 12:05:09 -0400 [thread overview]
Message-ID: <20091026160509.GA8755@Krystal> (raw)
In-Reply-To: <20091026071832.36405c9a@infradead.org>
* Arjan van de Ven (arjan@infradead.org) wrote:
> On Mon, 26 Oct 2009 09:17:49 -0400
> Pierre-Marc Fournier <pierre-marc.fournier@polymtl.ca> wrote:
>
> > Ingo Molnar wrote:
> > >
> > > But i also disagree with it on a technical level: code duplication
> > > is _bad_. Why does the code have to be duplicated in user-space
> > > like that? I'd like Linux tracing code to be in the kernel repo.
> > > Why isnt this done properly, as part of the kernel project - to
> > > make sure it all stays in sync?
> > >
> >
> > If you mean that this code should solely be used inside the kernel,
> > then what you propose technically does not work. There is a very high
> > cost to accessing kernel code from userspace.
>
> yeah 100 cycles is insanely high, that's at least the equivalent of...
> say one cache miss.
>
Hi Arjan,
Maybe it's just me, but if you are talking of system calls performed
with sysenter, my own machine (with an Intel Xeon E5405 CPU) seems to
disagree with your estimations:
For a system call doing basically _nothing_:
Cache-cold system call:
Time for a system call (returns after a simple test) :
TSC diff : 6426 cycles
time diff : 3212.53 ns
Cache-hot system call:
Time for system call (10000 calls) (returns after a simple test) :
TSC diff : 599.893 cycles per call
time diff : 299.903 ns per call
Otherwise, if you are instead referring to a vDSO, then the contexts is
slightly different, and it becomes cheaper, but it does not allow to
share code as much between the in-kernel and vDSO implementations,
mainly due to different locking required. Moreover, I wonder about the
maximum vDSO size that can be ported across multiple architectures. It
has only been used for really tiny pieces of code so far.
Thanks,
Mathieu
>
> --
> Arjan van de Ven Intel Open Source Technology Centre
> For development, discussion and tips for power savings,
> visit http://www.lesswatts.org
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2009-10-26 16:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 16:02 Relicensing tracepoints and markers to Dual LGPL v2.1/GPL v2, headers to Dual BSD/GPL Mathieu Desnoyers
2009-10-23 16:06 ` Mathieu Desnoyers
2009-10-24 21:03 ` Jesper Juhl
2009-10-24 21:22 ` Mathieu Desnoyers
2009-10-26 1:53 ` Wu Fengguang
2009-10-26 2:08 ` Relicensing tracepoints and markers to Dual LGPL v2.1/GPL v2,headers " Zhaolei
2009-10-26 5:03 ` GeunSik Lim
2009-10-26 7:30 ` Ingo Molnar
2009-10-26 8:10 ` GeunSik Lim
2009-10-26 10:17 ` Alan Cox
2009-10-26 11:31 ` Ingo Molnar
2009-10-26 13:45 ` Steven Rostedt
2009-10-26 13:40 ` Steven Rostedt
2009-10-26 13:17 ` Pierre-Marc Fournier
2009-10-26 13:29 ` Steven Rostedt
2009-10-26 16:11 ` Mathieu Desnoyers
2009-10-26 14:18 ` Arjan van de Ven
2009-10-26 16:05 ` Mathieu Desnoyers [this message]
2009-10-26 20:21 ` Ingo Molnar
2009-10-28 14:11 ` Mathieu Desnoyers
2009-10-23 16:31 ` Relicensing tracepoints and markers to Dual LGPL v2.1/GPL v2, headers " Ingo Molnar
2009-10-23 17:02 ` Mathieu Desnoyers
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=20091026160509.GA8755@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=arjan@infradead.org \
--cc=bunk@stusta.de \
--cc=dominique.toupin@ericsson.com \
--cc=fengguang.wu@intel.com \
--cc=fweisbec@gmail.com \
--cc=harvey.harrison@gmail.com \
--cc=jaswinderrajput@gmail.com \
--cc=jj@chaosbits.net \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=leemgs1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michel.dagenais@polymtl.ca \
--cc=mingo@elte.hu \
--cc=pierre-marc.fournier@polymtl.ca \
--cc=rostedt@goodmis.org \
--cc=rpjday@mindspring.com \
--cc=zhaolei@cn.fujitsu.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