From: Jiri Olsa <olsajiri@gmail.com>
To: lsf-pc@lists.linux-foundation.org
Cc: bpf <bpf@vger.kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
lorenz.bauer@isovalent.com,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [LSF/MM/BPF TOPIC] multi uprobe link
Date: Fri, 24 Feb 2023 11:25:17 +0100 [thread overview]
Message-ID: <Y/iQjSidojkAkNxj@krava> (raw)
We have a usecase to monitor potentially many uprobes and current way of
attaching many uprobes through perf takes long time. It's because there's
extra perf event install/schedule for each uprobe you want to attach.
It'd be great to have a another way to attach multiple uprobes probably by
adding new uprobe_multi link, that would create system wide uprobes directly
and attach bpf program to it.
Although that would not solve all the performance issues with uprobes, it
seems like a good start to solve attach/detach times.
I'd be interested in other people's experiences with uprobes and ideas on
speeding it up. The uprobe_multi link prototype should be done by that time,
hopefully ;-)
thanks,
jirka
next reply other threads:[~2023-02-24 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 10:25 Jiri Olsa [this message]
2023-02-24 17:57 ` [LSF/MM/BPF TOPIC] multi uprobe link 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=Y/iQjSidojkAkNxj@krava \
--to=olsajiri@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=lorenz.bauer@isovalent.com \
--cc=lsf-pc@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.