mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Vaibhav Shinde <v.bhav.shinde@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	tj@kernel.org, Davidlohr Bueso <dave@stgolabs.net>
Subject: Re: Preemptionirqsoff latency issue
Date: Fri, 9 Jan 2015 11:25:05 -0500	[thread overview]
Message-ID: <20150109112505.4ed9de41@gandalf.local.home> (raw)
In-Reply-To: <CAB5gotu75cXeHKhn-GShOTKW7=2bVdYfeUpxM7kCSTRWRsC79Q@mail.gmail.com>

On Fri, 9 Jan 2015 20:19:51 +0530
Vaibhav Shinde <v.bhav.shinde@gmail.com> wrote:

> Hi Peter,
> 
> Thanks for you reply.
> 
> I am interested in scheduling latency, and using ftrace I see for my
> application suffering from it, that's why I am digging in preemption/irq
> disable time which might cause the latency.
> 
> My app runs on cpu0, while other cpus looks idle; as per my understanding
> from your comment owner of the mutex is on the cpu other than cpu0, and
> which is causing wait spin on cpu0.
> Can this be the reason why latency is caused ?
> If so, then I think I need to take care of the mutex lock which is called
> from my code.
> 

If you download and install the latest trace-cmd, you may be able to
get more information with its new command "profile".

 # trace-cmd profile -o  file  workload

Then look at the output in file.

To limit the running to tracing only the workload:

 # trace-cmd profile -o file -F -c workload

You'll need to use the latest that's in my repo. Use the master branch,
as it has all the above features.

 git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git

-- Steve

  parent reply	other threads:[~2015-01-09 16:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAB5gottA3D_eJsHcGwO62fJtEqMqivX2kS5D-JhHphW9ADV88A@mail.gmail.com>
2015-01-09  9:56 ` Peter Zijlstra
     [not found]   ` <CAB5gotu75cXeHKhn-GShOTKW7=2bVdYfeUpxM7kCSTRWRsC79Q@mail.gmail.com>
2015-01-09 16:25     ` Steven Rostedt [this message]
2015-01-10  2:13     ` Davidlohr Bueso

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=20150109112505.4ed9de41@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=dave@stgolabs.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tj@kernel.org \
    --cc=v.bhav.shinde@gmail.com \
    /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

all inboxes | Powered by JetHome®