From: Jiri Olsa <jolsa@redhat.com>
To: David Ahern <dsahern@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
Andrew Jones <drjones@redhat.com>
Subject: Re: [PATCH 2/2] perf scripts: Fix rwtop record script
Date: Wed, 6 Feb 2013 13:48:40 +0100 [thread overview]
Message-ID: <20130206124840.GA11700@krava.redhat.com> (raw)
In-Reply-To: <51113018.80503@gmail.com>
On Tue, Feb 05, 2013 at 09:15:20AM -0700, David Ahern wrote:
> On 2/5/13 9:05 AM, Jiri Olsa wrote:
> >Adding -D option into the rwtop record command line, to get
> >immediate response when there's event in the buffer.
>
> Seems like this will dramatically increase CPU usage of perf-record
> as well as increase the overhead of each event with a process
> wakeup. How about a poll option on perf-record to have it wake up at
> a given rate instead?
right, I'll check
thanks,
jirka
prev parent reply other threads:[~2013-02-06 12:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 16:05 [PATCH 0/2] perf scripts: Fix rwtop script Jiri Olsa
2013-02-05 16:05 ` [PATCH 1/2] perf scripts: Fix SIGALRM and pipe read race for rwtop Jiri Olsa
2013-02-06 22:11 ` [tip:perf/core] perf perl " tip-bot for Jiri Olsa
2013-02-05 16:05 ` [PATCH 2/2] perf scripts: Fix rwtop record script Jiri Olsa
2013-02-05 16:15 ` David Ahern
2013-02-06 12:48 ` Jiri Olsa [this message]
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=20130206124840.GA11700@krava.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=drjones@redhat.com \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung@kernel.org \
--cc=paulus@samba.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.