From: Andrii Nakryiko <andrii@kernel.org>
To: linux-trace-kernel@vger.kernel.org, rostedt@goodmis.org,
mhiramat@kernel.org
Cc: bpf@vger.kernel.org, Andrii Nakryiko <andrii@kernel.org>
Subject: [PATCH 0/2] Objpool performance improvements
Date: Wed, 24 Apr 2024 14:52:12 -0700 [thread overview]
Message-ID: <20240424215214.3956041-1-andrii@kernel.org> (raw)
Improve objpool (used heavily in kretprobe hot path) performance with two
improvements:
- inlining performance critical objpool_push()/objpool_pop() operations;
- avoiding re-calculating relatively expensive nr_possible_cpus().
These opportunities were found when benchmarking and profiling kprobes and
kretprobes with BPF-based benchmarks. See individual patches for details and
results.
Andrii Nakryiko (2):
objpool: enable inlining objpool_push() and objpool_pop() operations
objpool: cache nr_possible_cpus() and avoid caching nr_cpu_ids
include/linux/objpool.h | 105 +++++++++++++++++++++++++++++++++++--
lib/objpool.c | 112 +++-------------------------------------
2 files changed, 107 insertions(+), 110 deletions(-)
--
2.43.0
next reply other threads:[~2024-04-24 21:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 21:52 Andrii Nakryiko [this message]
2024-04-24 21:52 ` [PATCH 1/2] objpool: enable inlining objpool_push() and objpool_pop() operations Andrii Nakryiko
2024-05-07 13:55 ` Vlastimil Babka
2024-05-10 7:59 ` wuqiang.matt
2024-05-10 8:20 ` Vlastimil Babka
2024-05-10 9:15 ` wuqiang.matt
2024-05-28 16:41 ` Masami Hiramatsu
2024-04-24 21:52 ` [PATCH 2/2] objpool: cache nr_possible_cpus() and avoid caching nr_cpu_ids Andrii Nakryiko
2024-05-28 20:30 ` Jiri Olsa
2024-04-26 14:25 ` [PATCH 0/2] Objpool performance improvements Masami Hiramatsu
2024-04-26 16:05 ` Andrii Nakryiko
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=20240424215214.3956041-1-andrii@kernel.org \
--to=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).