From: Christian Brauner <brauner@kernel.org>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] kcmp: improve performance adding an unlikely hint to task comparisons
Date: Thu, 13 Feb 2025 17:49:12 +0100 [thread overview]
Message-ID: <20250213-ablauf-rammen-ede462c247f6@brauner> (raw)
In-Reply-To: <20250213163916.709392-1-colin.i.king@gmail.com>
On Thu, 13 Feb 2025 16:39:16 +0000, Colin Ian King wrote:
> Adding an unlikely() hint on task comparisons on an unlikely error
> return path improves run-time performance of the kcmp system call.
>
> Benchmarking on an i9-12900 shows an improvement of ~5.5% on kcmp().
> Results based on running 20 tests with turbo disabled (to reduce
> clock freq turbo changes), with 10 second run per test and comparing
> the number of kcmp calls per second. The % Standard deviation of 20
> tests was ~0.25%, results are reliable.
>
> [...]
Applied to the vfs-6.15.misc branch of the vfs/vfs.git tree.
Patches in the vfs-6.15.misc branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.15.misc
[1/1] kcmp: improve performance adding an unlikely hint to task comparisons
https://git.kernel.org/vfs/vfs/c/a25b006052a7
prev parent reply other threads:[~2025-02-13 16:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 16:39 Colin Ian King
2025-02-13 16:49 ` Christian Brauner [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=20250213-ablauf-rammen-ede462c247f6@brauner \
--to=brauner@kernel.org \
--cc=colin.i.king@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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®