On Mon, Apr 18, 2022 at 01:06:36PM +0300, Mike Rapoport wrote: > Hi, > > On Sat, Apr 16, 2022 at 10:26:08PM +0000, Song Liu wrote: > > > On Apr 16, 2022, at 1:30 PM, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > > > > > > Maybe I am missing something, but I really don't think this is ready > > > for prime-time. We should effectively disable it all, and have people > > > think through it a lot more. > > > > This has been discussed on lwn.net: https://lwn.net/Articles/883454/. > > AFAICT, the biggest concern is whether reserving minimal 2MB for BPF > > programs is a good trade-off for memory usage. This is again my fault > > not to state the motivation clearly: the primary gain comes from less > > page table fragmentation and thus better iTLB efficiency. > > Reserving 2MB pages for BPF programs will indeed reduce the fragmentation, > but OTOH it will reduce memory utilization. If for large systems this may > not be an issue, on smaller machines trading off memory for iTLB > performance may be not that obvious. So the current optimization at best should be a kconfig option? > > Other folks (in recent thread on this topic and offline in other > > discussions) also showed strong interests in using similar technical > > for text of kernel modules. So I would really like to learn your > > opinion on this. There are many details we can optimize, but I guess > > the general mechanism has to be something like: > > - allocate a huge page, make it safe, and set it as executable; > > - as users (BPF, kernel module, etc.) request memory for text, give > > a chunk of the huge page to the user. > > - use some mechanism to update the chunk of memory safely. > > There are use-cases that require 4K pages with non-default permissions in > the direct map and the pages not necessarily should be executable. There > were several suggestions to implement caches of 4K pages backed by 2M > pages. Even if we just focus on the executable side of the story... there may be users who can share this too. I've gone down memory lane now at least down to year 2005 in kprobes to see why the heck module_alloc() was used. At first glance there are some old comments about being within the 2 GiB text kernel range... But some old tribal knowledge is still lost. The real hints come from kprobe work since commit 9ec4b1f356b3 ("[PATCH] kprobes: fix single-step out of line - take2"), so that the "For the %rip-relative displacement fixups to be doable"... but this got me wondering, would other users who *do* want similar funcionality benefit from a cache. If the space is limited then using a cache makes sense. Specially if architectures tend to require hacks for some of this to all work. Then, since it seems since the vmalloc area was not initialized, wouldn't that break the old JIT spray fixes, refer to commit 314beb9bcabfd ("x86: bpf_jit_comp: secure bpf jit against spraying attacks")? Is that sort of work not needed anymore? If in doubt I at least made the old proof of concept JIT spray stuff compile on recent kernels [0], but I haven't tried out your patches yet. If this is not needed anymore, why not? The collection of tribal knowedge around these sorts of things would be good to not loose and if we can share, even better. > I believe that "allocate huge page and split it to basic pages to hand out > to users" concept should be implemented at page allocator level and I > posted and RFC for this a while ago: > > https://lore.kernel.org/all/20220127085608.306306-1-rppt@xxxxxxxxxx/ Neat, so although eBPF is a big user, are there some use cases outside that immediately benefit? [0] https://github.com/mcgrof/jit-spray-poc-for-ksp LUis
