mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kayra Cizmeci <kayracizmeci@gmail.com>
To: vineethr@linux.ibm.com
Cc: bsegall@google.com, dietmar.eggemann@arm.com,
	juri.lelli@redhat.com, kayracizmeci@gmail.com,
	kprateek.nayak@amd.com, linux-kernel@vger.kernel.org,
	mgorman@suse.de, mingo@redhat.com, peterz@infradead.org,
	rostedt@goodmis.org, sh@gentwo.org, vincent.guittot@linaro.org,
	vschneid@redhat.com
Subject: Re: [PATCH] sched/fair: Let sync wakeups target the waker's core
Date: Tue, 11 Aug 2026 02:17:24 +0300	[thread overview]
Message-ID: <20260810231724.65791-1-kayracizmeci@gmail.com> (raw)
In-Reply-To: <b45fda9f-f7b2-453f-9211-987a7bd07b9f@linux.ibm.com>

Hi Vineeth,

I tested the things you wanted on the same box as before in the current 
baseline (d58772d8520c) and baseline + patch. 

command: perf bench sched pipe

baseline:
run 1: usecs/op: 1.435285, ops/sec: 696725
run 2: usecs/op: 1.305019, ops/sec: 765685
run 3: usecs/op: 1.143834, ops/sec: 874176
run 4: usecs/op: 1.549996, ops/sec: 645162
run 5: usecs/op: 1.136511, ops/sec: 879885

baseline + patch:
run 1: usecs/op: 1.362729, ops/sec: 733821
run 2: usecs/op: 1.420710, ops/sec: 703873
run 3: usecs/op: 1.229553, ops/sec: 813303
run 4: usecs/op: 1.453649, ops/sec: 687923
run 5: usecs/op: 1.204788, ops/sec: 839921

I don't think these numbers really mean anything.
Range is too big, as an example, on baseline the 
biggest usecs/op is 1.54996, while the smallest one 
is 1.136511. And this pattern just repeats itself.
The range is smaller on the baseline + patch,
but I don't really know what it means.

command: perf stat -r 10 -e cycles,cache-misses,L1-dcache-loads,L1-dcache-load-misses,cpu/event=0x64,umask=0x08/ 
perf bench sched pipe

I got the L1-dcache-load-misses and L1-dcache-loads from the perf list, as for the other one I got it from
tools/perf/pmu-events/arch/x86/amdzen3/recommended.json, l2_cache_misses_from_dc_misses.

I ran this once on both the baseline and baseline + patch since it runs 10 times with -r.

baseline: 

cycles: 12317680674
cache-misses: 19567069
L1-dcache-loads: 2792471451
L1-dcache-load-misses: 52924092
L2(event = 0x64, umask = 0x08): 18696435

baseline + patch:

cycles: 12304183071
cache-misses: 20105690
L1-dcache-loads: 2796772374
L1-dcache-load-misses: 50928594
L2(event = 0x64, umask = 0x08): 18928237

In the old test, the cycles decreased 1.40%, but in this one the cycles decreased 0.11%. Also
cache-misses increased 4.60% in the old test, but in this one it increased 2.75%.

I think this may be because the baseline is different, but that is just a guess.


I also tested LLC, or L3, same as L2 I got the values from /amdzen3/recommended.json, l3_misses.

baseline: 

L3(event=0x04, umask=0x01): 23064400

baseline + patch:

L3(event=0x04, umask=0x01): 22870280

L1-dcache-load-misses went down 3.77% while L2 went up 1.24% and
L3 went down 0.84%.

Also please drop the Tested-by, I'll retest on v2 and send a new one. 

Thanks, 
Kayra

      reply	other threads:[~2026-08-10 23:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-01  3:55 Madadi Vineeth Reddy
2026-08-01  6:43 ` Zhan Xusheng
2026-08-04  4:49 ` K Prateek Nayak
2026-08-04 12:13   ` Madadi Vineeth Reddy
2026-08-05  3:30     ` K Prateek Nayak
2026-08-06  4:50       ` Madadi Vineeth Reddy
2026-08-06 14:22         ` Chen Yu
2026-08-11  5:40           ` Madadi Vineeth Reddy
2026-08-06 13:03 ` Kayra Cizmeci
2026-08-10 15:01   ` Madadi Vineeth Reddy
2026-08-10 23:17     ` Kayra Cizmeci [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=20260810231724.65791-1-kayracizmeci@gmail.com \
    --to=kayracizmeci@gmail.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sh@gentwo.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vineethr@linux.ibm.com \
    --cc=vschneid@redhat.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®