On Wed, 5 Jun 2024 09:42:45 -0700 Andrii Nakryiko <andrii.nakryiko@xxxxxxxxx> wrote: > Another ping. It's been two weeks since Jiri posted the last revision > that got no more feedback to be addressed and everyone seems to be > happy with it. Sorry, there's been a lot going on. > > This is an important speed up improvement for uprobe infrastructure in > general and for BPF ecosystem in particular. "Uprobes are slow" is one > of the top complaints from production BPF users, and sys_uretprobe > approach is significantly improving the situation for return uprobes > (aka uretprobes), potentially enabling new use cases that previously > could have been too expensive to trace in practice and reducing the > overhead of the existing ones. > > I'd appreciate the engagement from linux-trace maintainers on this > patch set. Given it's important for BPF and that a big part of the > patch set is BPF-based selftests, we'd also be happy to route all this > through the bpf-next tree (which would actually make logistics for us > much easier, but that's not the main concern). But regardless of the > tree, it would be nice to make a decision and go forward with it. I'll be talking with Masami about this later today. -- Steve
