Re: [diamon-discuss] Diamon Meeting on Tuesday February 9th, 2016, at 11h EDT (15h UTC)
Alexei Starovoitov <[email protected]> Thu, 18 Feb 2016 20:40:22 +0100
| Newsgroups | dev.linux.lists.diamon-discuss |
|---|---|
| Message-ID | <CAADnVQ+8vc3qjwWcHmN8so1CD3eXH68nMbopT4nPkEqphU9uzA@mail.gmail.com> |
On Thu, Feb 18, 2016 at 2:44 PM, Mathieu Desnoyers <[email protected]> wrote: > Adding Alexei and Brendan in CC, they will likely be interested > in the eBPF discussion. yep :) please cc iovisor-dev as well for ideas you guys have around making use of bpf kernel bits with 'latency-tracker'. > ----- On Feb 17, 2016, at 11:41 PM, Julien Desfossez [email protected] wrote: > >> Hi, >> >> We are currently setting up a place on the diamon website so we can >> upload the slides, I will send the link soon. >> >> Regarding the mainlining, we intend to push this projet upstream. Before >> that, we are working on more measurements/benchmarks, stability testing >> and usability improvements. >> >> Also, one things that we would like to investigate before sending the >> patches is the possibility of using eBPF/bcc to handle the probes while >> keeping the latency-tracker as the backend to keep the state and all the >> more advanced interactions with the kernel. That way, we could combine >> the flexibility/safety of eBPF and the efficiency of the >> latency-tracker. >> >> Thanks for your feedback, I will keep this list updated of the progress >> we make on that front. >> >> Julien >> >> On 14-Feb-2016 11:37:44 AM, Al Grant wrote: >>> Hi, >>> >>> I have read the blog and this looks a very useful technique but unfortunately I >>> couldn't make the call. Are slides/minutes available? >>> >>> My main question is not actually technical - it's about the prospects for >>> getting >>> this into mainline Linux. >>> >>> Thanks, >>> >>> Al >>> >>> >>> > -----Original Message----- >>> > From: [email protected] [mailto:diamon- >>> > [email protected]] On Behalf Of Julien Desfossez >>> > Sent: 08 February 2016 19:14 >>> > To: Mathieu Desnoyers >>> > Cc: [email protected] >>> > Subject: Re: [diamon-discuss] Diamon Meeting on Tuesday February 9th, 2016, >>> > at 11h EDT (15h UTC) >>> > >>> > 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 >>> > _______________________________________________ >>> > diamon-discuss mailing list >>> > [email protected] >>> > https://lists.linuxfoundation.org/mailman/listinfo/diamon-discuss >>> >>> IMPORTANT NOTICE: The contents of this email and any attachments are >>> confidential and may also be privileged. If you are not the intended recipient, >>> please notify the sender immediately and do not disclose the contents to any >>> other person, use it for any purpose, or store or copy the information in any >>> medium. Thank you. > > -- > Mathieu Desnoyers > EfficiOS Inc. > http://www.efficios.com