linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ruben Ayrapetyan <Ruben.Ayrapetyan@arm.com>
To: James Clark <James.Clark@arm.com>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"acme@kernel.org" <acme@kernel.org>,
	Mark Rutland <Mark.Rutland@arm.com>,
	"alexander.shishkin@linux.intel.com" 
	<alexander.shishkin@linux.intel.com>,
	"jolsa@redhat.com" <jolsa@redhat.com>,
	"namhyung@kernel.org" <namhyung@kernel.org>
Cc: "linux-perf-users@vger.kernel.org"
	<linux-perf-users@vger.kernel.org>,
	"leo.yan@linaro.com" <leo.yan@linaro.com>,
	Suzuki Poulose <Suzuki.Poulose@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 1/1] perf/core: Wake up parent event if inherited event has no ring buffer
Date: Mon, 24 Jan 2022 11:37:43 +0000	[thread overview]
Message-ID: <AM9PR08MB60200FA42FAB6DB843718F0A975E9@AM9PR08MB6020.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20211206113840.130802-2-james.clark@arm.com>

Hi everyone,

I've tried running a benchmark with and without this patch applied, with the following options:
 perf record -e arm_spe_0/event_filter=0,jitter=0,ts_enable=1,pa_enable=0,min_latency=0/ ...
repeating it 60 times with and without the patch.

Without the patch, the output perf.data sizes were: 1.0G 1.0G 1.0G 1.0G 1.0G 1.0G 1.0G 1.0G 47M 48M 48M 48M 48M 48M 48M 48M 48M 48M 49M 49M 49M 49M 49M 49M 49M 49M 49M 49M 49M 49M 49M 49M 49M 49M 49M 60M 60M 60M 60M 61M 61M 61M 61M 61M 61M 61M 62M 62M 62M 62M 62M 62M 62M 62M 62M 63M 63M 63M 65M 990M i.e. 47MB to 1.0GB

With the patch, the output sizes were: 1.4G 1.4G 1.4G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G 1.5G i.e. 1.4GB to 1.5GB.

Tested-by: Ruben Ayrapetyan <Ruben.Ayrapetyan@arm.com>
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

  reply	other threads:[~2022-01-24 11:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06 11:38 [RFC PATCH 0/1] perf/core: Wake up parent event if inherited event has no ring buffer James Clark
2021-12-06 11:38 ` [RFC PATCH 1/1] " James Clark
2022-01-24 11:37   ` Ruben Ayrapetyan [this message]
2022-01-24 11:49   ` Peter Zijlstra
2022-01-24 14:58     ` James Clark
2022-01-25 19:12       ` Peter Zijlstra
2022-01-26 16:15         ` James Clark
2022-01-27 11:50   ` [tip: perf/urgent] perf: Always wake the parent event tip-bot2 for James Clark

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=AM9PR08MB60200FA42FAB6DB843718F0A975E9@AM9PR08MB6020.eurprd08.prod.outlook.com \
    --to=ruben.ayrapetyan@arm.com \
    --cc=James.Clark@arm.com \
    --cc=Mark.Rutland@arm.com \
    --cc=Suzuki.Poulose@arm.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=leo.yan@linaro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).