From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 9 Feb 2016 16:02:03 +0000 (UTC) From: Mathieu Desnoyers Message-ID: <1138931746.15039.1455033723118.JavaMail.zimbra@efficios.com> In-Reply-To: <20160208191332.GJ26639@sinkpad.internal.efficios.com> References: <1478740846.7068.1454011725322.JavaMail.zimbra@efficios.com> <20160208191332.GJ26639@sinkpad.internal.efficios.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [diamon-discuss] Diamon Meeting on Tuesday February 9th, 2016, at 11h EDT (15h UTC) List-Id: DiaMon diagnostic and monitoring workgroup general discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: diamon-discuss@lists.linuxfoundation.org The conference call is starting now. See you there, Thanks, Mathieu ----- On Feb 8, 2016, at 2:13 PM, Julien Desfossez jdesfossez@efficios.com wrote: > Hi, > > Here is the information for tomorrow's call: > February 9th, 2016, at 11h EDT (15h UTC) > > Conference: 415-906-5657 PIN: 88326 > URL for the screen sharing: www.uberconference.com/mdolan > > Local International phone numbers are available at: > https://www.uberconference.com/international > > Please note anyone dialing using the international numbers need to dial > the local international number for the country they are in, then enter > the US conference number (4159065657), and then enter the PIN > (88326). > > Julien > > On 28-Jan-2016 08:08:45 PM, Mathieu Desnoyers wrote: >> 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 -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com