From: peter enderborg <peter.enderborg@sony.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Mel Gorman <mgorman@techsingularity.net>,
Michal Hocko <mhocko@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Alex Deucher <alexander.deucher@amd.com>,
"David S . Miller" <davem@davemloft.net>,
Harry Wentland <Harry.Wentland@amd.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tony Cheng <Tony.Cheng@amd.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
Pavel Tatashin <pasha.tatashin@oracle.com>
Subject: Re: [PATCH] Add slowpath enter/exit trace events
Date: Fri, 24 Nov 2017 08:43:47 +0100 [thread overview]
Message-ID: <16719b9b-b7e2-3cce-299b-99215b79518f@sony.com> (raw)
In-Reply-To: <640b7de7-c216-de34-18e8-dc1aacd19f35@I-love.SAKURA.ne.jp>
On 11/23/2017 02:43 PM, Tetsuo Handa wrote:
> Please see my attempt at
> http://lkml.kernel.org/r/1510833448-19918-1-git-send-email-penguin-kernel@I-love.SAKURA.ne.jp .
> Printing just current thread is not sufficient for me.
>
>
Seems to me that it is a lot more overhead with timers and stuff.
My probe is for the health of the system trying to capture how get the penalty and how much. A slowpath alloc in a audio stream can causes drop-outs. And they are very hard to debug in userspace.
next prev parent reply other threads:[~2017-11-24 7:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 10:43 [PATCH] Add slowpath enter/exit trace events peter.enderborg
2017-11-23 12:25 ` Michal Hocko
2017-11-23 12:35 ` peter enderborg
2017-11-23 12:47 ` Michal Hocko
2017-11-23 13:03 ` peter enderborg
2017-11-23 13:47 ` Michal Hocko
2017-11-23 13:36 ` Mel Gorman
2017-11-23 13:43 ` Tetsuo Handa
2017-11-24 7:43 ` peter enderborg [this message]
2017-11-23 14:01 ` Michal Hocko
2017-11-23 15:09 ` Mel Gorman
2017-11-24 8:38 ` peter enderborg
2017-11-23 13:00 ` Tetsuo Handa
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=16719b9b-b7e2-3cce-299b-99215b79518f@sony.com \
--to=peter.enderborg@sony.com \
--cc=Harry.Wentland@amd.com \
--cc=Tony.Cheng@amd.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.deucher@amd.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=mingo@redhat.com \
--cc=pasha.tatashin@oracle.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=rostedt@goodmis.org \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).