From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Andrii Nakryiko <andrii@kernel.org>
Cc: linux-trace-kernel@vger.kernel.org, rostedt@goodmis.org,
bpf@vger.kernel.org, wuqiang.matt <wuqiang.matt@bytedance.com>
Subject: Re: [PATCH 0/2] Objpool performance improvements
Date: Fri, 26 Apr 2024 23:25:39 +0900 [thread overview]
Message-ID: <20240426232539.faf453fb71e6af7017c7967b@kernel.org> (raw)
In-Reply-To: <20240424215214.3956041-1-andrii@kernel.org>
Hi Andrii,
On Wed, 24 Apr 2024 14:52:12 -0700
Andrii Nakryiko <andrii@kernel.org> wrote:
> 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().
Thanks for optimizing objpool. Both looks good to me.
BTW, I don't intend to stop this short-term optimization attempts,
but I would like to ask you check the new fgraph based fprobe
(kretprobe-multi)[1] instead of objpool/rethook.
[1] https://lore.kernel.org/all/171318533841.254850.15841395205784342850.stgit@devnote2/
I'm considering to obsolete the kretprobe (and rethook) with fprobe
and eventually remove it. Those have similar feature and we should
choose safer one.
Thank you,
>
> 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
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2024-04-26 14:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 21:52 [PATCH 0/2] Objpool performance improvements Andrii Nakryiko
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 ` Masami Hiramatsu [this message]
2024-04-26 16:05 ` [PATCH 0/2] Objpool performance improvements 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=20240426232539.faf453fb71e6af7017c7967b@kernel.org \
--to=mhiramat@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=wuqiang.matt@bytedance.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;
as well as URLs for NNTP newsgroup(s).