From: "Chanho Park" <chanho61.park@samsung.com>
To: <linux-rt-users@vger.kernel.org>
Cc: <bigeasy@linutronix.de>, "'Thomas Gleixner'" <tglx@linutronix.de>
Subject: hackbench score comparison between 5.10.75-rt47 and 5.14.14-rt21
Date: Wed, 3 Nov 2021 12:15:49 +0900 [thread overview]
Message-ID: <009301d7d061$1a1bbeb0$4e533c10$@samsung.com> (raw)
In-Reply-To: CGME20211103031549epcas2p34418a4e6218ca93da57a0c373691bd41@epcas2p3.samsung.com
Dear RT folks,
I found an uncomprehended value of hackbench while I tested preempt rt
patches on my ARM64(Cortex A76 x 8) target.
So, I decided to check it on QEMU x86_64 KVM with yocto. I executed both
images with below command.
$ runqemu qemux86-64 kvm nographic qemuparams="-smp cores=4"
I was able to get similar score values with my arm64 target. It was half
than 5.10.75 kernel like below.
Any idea about this? Actually, I'm not sure it could be a regression or not.
<5.10.75-rt47>
root@qemux86-64:~# hackbench -l 10000
Running in process mode with 10 groups using 40 file descriptors each (==
400 tasks)
Each sender will pass 10000 messages of 100 bytes
Time: 49.898
<5.14.14-rt21>
root@qemux86-64:~# hackbench -l 10000
Running in process mode with 10 groups using 40 file descriptors each (==
400 tasks)
Each sender will pass 10000 messages of 100 bytes
Time: 96.973
Best Regards,
Chanho Park
next parent reply other threads:[~2021-11-03 3:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20211103031549epcas2p34418a4e6218ca93da57a0c373691bd41@epcas2p3.samsung.com>
2021-11-03 3:15 ` Chanho Park [this message]
2021-11-03 9:13 ` hackbench score comparison between 5.10.75-rt47 and 5.14.14-rt21 Sebastian Andrzej Siewior
2021-11-05 1:41 ` Chanho Park
2021-11-12 14:00 ` 'Sebastian Andrzej Siewior'
2021-11-16 9:37 ` Vlastimil Babka
2021-11-16 9:42 ` 'Sebastian Andrzej Siewior'
2021-11-16 13:42 ` Chanho Park
2021-11-19 11:12 ` 'Sebastian Andrzej Siewior'
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='009301d7d061$1a1bbeb0$4e533c10$@samsung.com' \
--to=chanho61.park@samsung.com \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.