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, 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,
	Kayra Cizmeci <kayracizmeci@gmail.com>
Subject: Re: [PATCH] sched/fair: Let sync wakeups target the waker's core
Date: Thu,  6 Aug 2026 16:03:24 +0300	[thread overview]
Message-ID: <20260806130326.79538-1-kayracizmeci@gmail.com> (raw)
In-Reply-To: <20260801035532.260625-1-vineethr@linux.ibm.com>

Hi Vineeth,

Since all the numbers on this thread are from POWER, I ran this on x86 (Zen 3). I ran the test 3 times on both
baseline and baseline + patch. 

I first got the baseline from 0d83957076 that was like that: 

=num===cycles===cache-misses= 
[ 1: 11266587459: 19064897  ]
[ 2: 11329575367: 18860444  ]
[ 3: 11283159019: 19121436  ]

Then, I got the 0d83957076 + this patch:

=num===cycles===cache-misses=
[ 1: 11128721747: 19886131  ]
[ 2: 11163014797: 20019508  ]
[ 3: 11111832330: 19764849  ]

I tested them with AMD Ryzen 7 5700X 8 Cores, 16 Threads or by other means SMT2. Busybox, minimal initramfs and 
perf or to be more specific, this command: perf stat -r 10 -e cycles,cache-misses perf bench sched pipe

There is a 1.40% decrease of cycles baseline to this patch while there is a 4.60% increase in cache-misses. 
Both of these values are average values of the decrease and the increase. The values also don't overlap.

I don't really have explanations for why this values came back like that, 
I wasn't expecting them to be like this. Especially cache-misses.

Tested-by: Kayra Cizmeci <kayracizmeci@gmail.com>

Thanks,
Kayra

  parent reply	other threads:[~2026-08-06 13:04 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 [this message]
2026-08-10 15:01   ` Madadi Vineeth Reddy
2026-08-10 23:17     ` Kayra Cizmeci

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=20260806130326.79538-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®