From: Mike Galbraith <efault@gmx.de>
To: ema@debian.org, linux-kernel@vger.kernel.org
Cc: Michal Hocko <mhocko@suse.com>
Subject: Re: Runtime overhead of PREEMPT_DYNAMIC
Date: Fri, 20 Oct 2023 14:42:22 +0200 [thread overview]
Message-ID: <7a818250a8f36476f13b57a172fdb1ab23645edc.camel@gmx.de> (raw)
In-Reply-To: <ZTJFA_Ac6nWawIHb@ariel>
On Fri, 2023-10-20 at 11:14 +0200, Emanuele Rocca wrote:
>
> Results of the tbench benchmark:
>
> - PREEMPT_DYNAMIC=n Throughput 3831.82 MB/sec
> - PREEMPT_DYNAMIC=y Throughput 3006.54 MB/sec
> - 20% performance degradation with PREEMPT_DYNAMIC
>
> All the tests above were performed using Linux 6.5.6 on a AMD Ryzen 7 3700X
> 8-Core CPU.
>
> Could someone please confirm whether the approach above seems sane and perhaps
> try and reproduce the results?
FWIW I can't reproduce anything like those crazy tbench numbers. It's
neither free nor crazy expensive here. It's kinda hard to imagine the
author's mailbox surviving submission day were it _that_ horrid, surely
something is amiss.
i7-4790 (quad+smt) avg cmdline
6.5.8-voluntary 3685.08 3679.93 3704.98 3689.99 1.000
6.5.8-dynamic 3571.62 3568.61 3550.55 3563.59 .965
3651.37 3599.87 3615.18 3622.14 .981 preempt=none
3459.58 3514.09 3539.88 3504.51 .949 preempt=full
voluntary (my usual)
CONFIG_PREEMPT_VOLUNTARY_BUILD=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
# CONFIG_PREEMPT_DYNAMIC is not set
dynamic (same config, just flip dynamic switch)
CONFIG_PREEMPT_BUILD=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_COUNT=y
CONFIG_PREEMPTION=y
CONFIG_PREEMPT_DYNAMIC=y
next prev parent reply other threads:[~2023-10-20 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 9:14 Emanuele Rocca
2023-10-20 12:42 ` Mike Galbraith [this message]
2023-10-20 13:40 ` Emanuele Rocca
2023-10-20 14:11 ` Mike Galbraith
2023-10-20 14:34 ` Mike Galbraith
2023-10-20 14:45 ` Emanuele Rocca
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=7a818250a8f36476f13b57a172fdb1ab23645edc.camel@gmx.de \
--to=efault@gmx.de \
--cc=ema@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.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®