From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: diamon-discuss@lists.linuxfoundation.org
Subject: [diamon-discuss] Diamon Meeting on Tuesday February 9th, 2016, at 11h EDT (15h UTC)
Date: Thu, 28 Jan 2016 20:08:45 +0000 (UTC) [thread overview]
Message-ID: <1478740846.7068.1454011725322.JavaMail.zimbra@efficios.com> (raw)
Hi,
Following the blog post published two weeks ago [1], we would like to
propose organizing a phone meeting with all interested members of this
workgroup on February 9th to gather feedback and ideas for improvement
on the subject of measuring and detecting high response time.
At EfficiOS, we have developed a kernel module for monitoring at run-time
the delay between the moment the kernel starts processing an interrupt
(do_IRQ) and the moment the target task gets scheduled in or has finished
processing the data.
When a high latency is detected, it emits a tracepoint event and can
wakeup a user-space script to take arbitrary actions as soon as
possible.
The main intent is to provide an entry point in a kernel trace. After
that, everyone has their own methodology to process the trace. The blog
post illustrates what we can do with LTTng as an example but the
detection and triggers are not coupled with any tracer.
The proposed agenda is a discussion around these points:
- presentation of the scope of the problem
- limitation of the current tools
- overview of the latency_tracker module applied for this use-case
-- current state
-- use-cases
-- future plans
- from the audience: comments, ideas, other approaches, etc.
If you have other points you would like to discuss around this subject,
please let me know and I will add them.
Also, if you wish to attend but can't make it at the proposed date and
time, let us know.
The details for the conference call will be sent soon.
Thanks,
Julien & Mathieu
[1] https://lttng.org/blog/2016/01/06/monitoring-realtime-latencies/
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next reply other threads:[~2016-01-28 20:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 20:08 Mathieu Desnoyers [this message]
2016-02-04 9:31 ` [diamon-discuss] Diamon Meeting on Tuesday February 9th, 2016, at 11h EDT (15h UTC) Oberhuber, Martin
2016-02-08 19:00 ` Julien Desfossez
2016-02-16 21:15 ` Mathieu Desnoyers
2016-02-16 21:22 ` Julien Desfossez
2016-02-16 21:37 ` Michael Dolan
2016-02-08 19:13 ` Julien Desfossez
2016-02-09 16:02 ` Mathieu Desnoyers
2016-02-14 11:37 ` Al Grant
2016-02-18 4:41 ` Julien Desfossez
2016-02-18 13:44 ` Mathieu Desnoyers
-- strict thread matches above, loose matches on Subject: below --
2016-02-18 19:40 Alexei Starovoitov
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=1478740846.7068.1454011725322.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=diamon-discuss@lists.linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.