From: Julien Desfossez <jdesfossez@efficios.com>
To: "Oberhuber, Martin" <Martin.Oberhuber@windriver.com>
Cc: "diamon-discuss@lists.linuxfoundation.org"
<diamon-discuss@lists.linuxfoundation.org>
Subject: Re: [diamon-discuss] Diamon Meeting on Tuesday February 9th, 2016, at 11h EDT (15h UTC)
Date: Mon, 8 Feb 2016 14:00:49 -0500 [thread overview]
Message-ID: <20160208190049.GI26639@sinkpad.internal.efficios.com> (raw)
In-Reply-To: <146B1557584B0B4DBD25ABAD45EF70F0F6E5164C@ALA-MBB.corp.ad.wrs.com>
Hi,
> I don't think I would have much to contribute, but I am certainly
> interested in what others say. Could the session be recorded, or
> meeting notes posted? - Otherwise I'd be available from the 15th on,
> in case you'd consider moving the session.
We did not receive any other requests for moving the meeting, so we will
do it tomorrow, I will try to record it.
> Two questions came up for me when reading the blog,
>
> 1. Julien writes "We are not trying to solve a problem related to the interrupts
> being masked for too long (ftrace already has some tools to help with that)."
> Which are those tools? Any pointer would be appreciated.
I was refering to the irqsoff tracer in ftrace.
> 2. I really like the general usefulness of the latency_tracker and the many clever
> ways it can be configured / leveraged - but it feels like an expert tool to me,
> where you'd very clearly have to know what you're doing. Are there any ideas
> making such expert tools more usable and discoverable by general users ?
Indeed for now it is not very user-friendly as we are still defining all
the knobs that we want to expose to the users. When we will have
gathered enough feedback we will see if how we can adapt this to make it
more easy to approach.
Thanks for the feedback,
Julien
next prev parent reply other threads:[~2016-02-08 19:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 20:08 [diamon-discuss] Diamon Meeting on Tuesday February 9th, 2016, at 11h EDT (15h UTC) Mathieu Desnoyers
2016-02-04 9:31 ` Oberhuber, Martin
2016-02-08 19:00 ` Julien Desfossez [this message]
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=20160208190049.GI26639@sinkpad.internal.efficios.com \
--to=jdesfossez@efficios.com \
--cc=Martin.Oberhuber@windriver.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.