public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: "Liang, Kan" <kan.liang@intel.com>,
	"acme@kernel.org" <acme@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"eranian@google.com" <eranian@google.com>,
	jolsa@kernel.org
Subject: Re: [PATCH 1/1] perf, tool: partial callgrap and time support in perf record
Date: Wed, 18 Mar 2015 16:14:06 +0900	[thread overview]
Message-ID: <20150318071406.GS943@sejong> (raw)
In-Reply-To: <20150316204826.GK31334@tassilo.jf.intel.com>

Hi Andi,

(Add Jiri to CC)

On Mon, Mar 16, 2015 at 01:48:26PM -0700, Andi Kleen wrote:
> On Mon, Mar 16, 2015 at 08:35:30PM +0000, Liang, Kan wrote:
> > > On Fri, Mar 13, 2015 at 02:18:07AM +0000, kan.liang@intel.com wrote:
> > > > From: Kan Liang <kan.liang@intel.com>
> > > >
> > > > When multiple events are sampled it may not be needed to collect
> > > > callgraphs for all of them. The sample sites are usually nearby, and
> > > > it's enough to collect the callgraphs on a reference event (such as
> > > > precise cycles or precise instructions). Similarly we also don't need
> > > > fine grained time stamps on all events, as it's enough to have time
> > > > stamps on the regular reference events. This patchkit adds the ability
> > > > to turn off callgraphs and time stamps per event. This in term can
> > > > reduce sampling overhead and the size of the perf.data (add some data)
> > > 
> > > Have you taken a look into group sampling feature?
> > > (e.g. perf record -e '{ev1,ev2}:S')
> > > 
> > 
> > I didn't find any issues when running group read. 
> > The patch doesn't change the behavior of group read features.
> > 
> > Did you observe any issues after applying the patch?
> 
> I think Namhyungs questions was if group read can be used
> instead to decrease the data size.

Right!


> 
> The answer is no: it solves a different problem. Group read 
> is just fine granuality counting. It cannot be used
> to sample for multiple events in parallel.

But group read disables sampling for non-leader events so the number
of total samples should be small, no?

Thanks,
Namhyung

  reply	other threads:[~2015-03-18  7:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13  2:18 [PATCH 1/1] perf, tool: partial callgrap and time support in perf record kan.liang
2015-03-16  2:03 ` Namhyung Kim
2015-03-16 20:35   ` Liang, Kan
2015-03-16 20:48     ` Andi Kleen
2015-03-18  7:14       ` Namhyung Kim [this message]
2015-03-18 19:18         ` Andi Kleen

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=20150318071406.GS943@sejong \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox