[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZfF02HCzYLcuwmw9@krava>
Date: Wed, 13 Mar 2024 10:41:44 +0100
From: Jiri Olsa <olsajiri@...il.com>
To: Andrii Nakryiko <andrii@...nel.org>
Cc: linux-trace-kernel@...r.kernel.org, rostedt@...dmis.org,
mhiramat@...nel.org, bpf@...r.kernel.org,
mathieu.desnoyers@...icios.com, linux-kernel@...r.kernel.org,
oleg@...hat.com
Subject: Re: [PATCH bpf-next 0/3] uprobes: two common case speed ups
On Tue, Mar 12, 2024 at 02:02:30PM -0700, Andrii Nakryiko wrote:
> This patch set implements two speed ups for uprobe/uretprobe runtime execution
> path for some common scenarios: BPF-only uprobes (patches #1 and #2) and
> system-wide (non-PID-specific) uprobes (patch #3). Please see individual
> patches for details.
>
> Given I haven't worked with uprobe code before, I'm unfamiliar with
> conventions in this subsystem, including which kernel tree patches should be
> sent to. For now I based all the changes on top of bpf-next/master, which is
> where I tested and benchmarked everything anyways. Please advise what should
> I use as a base for subsequent revision. Thanks.
>
> Andrii Nakryiko (3):
> uprobes: encapsulate preparation of uprobe args buffer
> uprobes: prepare uprobe args buffer lazily
> uprobes: add speculative lockless system-wide uprobe filter check
nice cleanup and speed up, lgtm
Reviewed-by: Jiri Olsa <jolsa@...nel.org>
jirka
>
> kernel/trace/trace_uprobe.c | 103 ++++++++++++++++++++++--------------
> 1 file changed, 63 insertions(+), 40 deletions(-)
>
> --
> 2.43.0
>
>
Powered by blists - more mailing lists