From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: linux-kernel@vger.kernel.org
Subject: [CFP] Tracing Summit 2016 Call for Presentations, October 12th, 2016, Berlin, Germany
Date: Wed, 04 May 2016 15:23:14 -0400 [thread overview]
Message-ID: <E1ay2OA-000127-Ni@thinkos> (raw)
Hi,
This is a call for presentations for the Tracing Summit which will be
held in Berlin, Germany, on October 12th, 2016, at the Maritim Hotel
Berlin. This event is co-located with Embedded Linux Conference 2016.
The Tracing Summit is organized by the Linux Foundation Diagnostic and
Monitoring Workgroup (http://diamon.org). 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 July 15th, 2016, 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:
* Investigation workflow of Real-Time, latency, and throughput issues,
* 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). Please understand that this open forum is not the proper
place to present sales or marketing pitches, nor technologies which are
prevented from being freely used in open source.
There is a single track, containing presentations between 30 and 45
minutes per subject with discussion.
This year, attending the Tracing Summit is free of charge, and attendees
are not required to register to other events. If you indend to attend,
we recommend you don't wait too much before registering
[https://www.regonline.com/tracingsummit16], as we need to consider room
size limits.
The Tracing Summit is currently sponsored by EfficiOS. Please let us
know if your company is interested in sponsoring this event.
See the Tracing Summit 2016 wiki at
http://www.tracingsummit.org/wiki/TracingSummit2016 for details.
Thank you,
On behalf of the Diagnostic and Monitoring Workgroup,
Dominique Toupin & Mathieu Desnoyers
reply other threads:[~2016-05-04 19:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1ay2OA-000127-Ni@thinkos \
--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