From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: linux-kernel@vger.kernel.org
Cc: submission@tracingsummit.org
Subject: [CFP] Tracing Summit 2014 Call for Presentations, October 13th, 2014, Düsseldorf, Germany
Date: Fri, 11 Jul 2014 21:08:44 +0000 (UTC) [thread overview]
Message-ID: <108406797.13221.1405112924516.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <1637700547.13216.1405112800501.JavaMail.zimbra@efficios.com>
Hi,
We are organizing a tracing summit in Düsseldorf, Germany, on
October 13, 2014, at the Congress Centre Düsseldorf. This event is
colocated with LinuxCon Europe 2014.
This event focuses on the tracing area, gathering people involved in
development and end-users of tracing tools as well as trace analysis
tools. The main target of this Tracing Summit is to provide room for
discussion between people in the various areas that benefit from
tracing, namely parallel, distributed and/or real-time systems, as well
as kernel development.
If you are interested to present, please submit a proposal to
submission@tracingsummit.org before August 31, 2014, at 23:59 EST.
Please provide a title, abstract describing the proposed talk
(900 characters maximum), short biography (900 characters maximum),
and describe the targeted audience (900 characters maximum).
We are welcoming presentations from both end users and developers, on
topics covering, but not limited to:
* Trace collection and extraction,
* Trace filtering,
* Trace aggregation,
* Trace formats,
* Tracing multi-core systems,
* Trace abstraction,
* Trace modeling,
* Automated trace analysis (e.g. dependency analysis),
* Tracing large clusters and distributed systems,
* Hardware-level tracing (e.g. DSP, GPU, bare-metal),
* Trace visualisation,
* Interaction between debugging and tracing,
* Tracing remote control,
* Analysis of large trace datasets,
* Cloud trace collection and analysis,
* Integration between trace tools,
* Live tracing & monitoring.
Those can cover recently available technologies, ongoing work, and yet
non-existing technologies (which are compellingly interesting to
end-users).
There is a single track, containing presentations between 30 and 45
minutes per subject with discussion.
Registration to LinuxCon Europe 2014 or CloudOpen Europe 2014 is
required in order to register to the Tracing Summit 2014. All
registration passes, including the new Attendee Networking Pass
registration, will allow you to register for the Tracing Summit. The
Tracing Summit registration access code will be provided on your
LinuxCon/CloudOpen registration confirmation page. The Tracing Summit
2014 has no entrance fees for LinuxCon/CouldOpen attendees.
We recommend you register to either or both events before August 1st,
2014 to benefit from early registration fees.
See the Tracing Summit 2014 wiki at
http://www.tracingsummit.org/wiki/TracingSummit2014 for details.
Thank you,
Dominique Toupin & Mathieu Desnoyers
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
parent reply other threads:[~2014-07-11 21:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1637700547.13216.1405112800501.JavaMail.zimbra@efficios.com>]
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=108406797.13221.1405112924516.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=linux-kernel@vger.kernel.org \
--cc=submission@tracingsummit.org \
/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