On Fri, 9 May 2025 16:28:55 -0700 Shakeel Butt <shakeel.butt@xxxxxxxxx> wrote: > BPF programs can trigger memcg charged kernel allocations in nmi > context. However memcg charging infra for kernel memory is not equipped > to handle nmi context. This series adds support for kernel memory > charging for nmi context. The patchset adds quite a bit of material to core MM on behalf of a single caller. So can we please take a close look at why BPF is doing this? What would be involved in changing BPF to avoid doing this, or of changing BPF to handle things locally? What would be the end-user impact of such an alteration? IOW, what is the value to our users of the present BPF behavior?
