From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, josh@joshtriplett.org,
dvhltc@us.ibm.com, niv@us.ibm.com, tglx@linutronix.de,
peterz@infradead.org, rostedt@goodmis.org,
Valdis.Kletnieks@vt.edu, dhowells@redhat.com
Subject: Re: [PATCH tip/core/rcu 1/2] rcu: 1Q2010 update for RCU documentation
Date: Thu, 14 Jan 2010 21:01:31 -0500 [thread overview]
Message-ID: <20100115020131.GA20934@Krystal> (raw)
* Paul E. McKenney (paulmck@linux.vnet.ibm.com) wrote:
> Add expedited functions. Review documentation and update obsolete
> verbiage. Also fix the advice for the RCU CPU-stall kernel configuration
> parameter, and document RCU CPU-stall warnings.
> ---
[...]
> +
> +@phdthesis{MathieuDesnoyersPhD
> +, title = "Low-impact Operating System Tracing"
Hi Paul,
Just for the sake of it, the title of my dissertation is, more
precisely:
+, title = "Low-Impact Operating System Tracing"
The final version is available at:
http://www.lttng.org/pub/thesis/desnoyers-dissertation-2009-12-v24.pdf
(and yes, it is in English) ;-)
Thanks,
Mathieu
> +, author = "Mathieu Desnoyers"
> +, school = "Ecole Polytechnique de Montr\'{e}al"
> +, month = "December"
> +, year = 2009
> +}
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next reply other threads:[~2010-01-15 2:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 2:01 Mathieu Desnoyers [this message]
2010-01-15 2:30 ` [PATCH tip/core/rcu 1/2] rcu: 1Q2010 update for RCU documentation Paul E. McKenney
2010-01-15 16:17 ` Mathieu Desnoyers
-- strict thread matches above, loose matches on Subject: below --
2010-01-15 0:10 [PATCH tip/core/rcu 0/2] Update RCU documentation and fix sparse warnings Paul E. McKenney
2010-01-15 0:10 ` [PATCH tip/core/rcu 1/2] rcu: 1Q2010 update for RCU documentation Paul E. McKenney
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=20100115020131.GA20934@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=paulmck@linux.vnet.ibm.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