On Mon, Nov 14, 2022 at 05:30:39PM -0800, Song Liu wrote: > On Mon, Nov 7, 2022 at 2:41 PM Song Liu <song@xxxxxxxxxx> wrote: > > > > [...] > > > > > > > This set enables bpf programs and bpf dispatchers to share huge pages with > > new API: > > execmem_alloc() > > execmem_alloc() > > execmem_fill() > > > > The idea is similar to Peter's suggestion in [1]. > > > > execmem_alloc() manages a set of PMD_SIZE RO+X memory, and allocates these > > memory to its users. execmem_alloc() is used to free memory allocated by > > execmem_alloc(). execmem_fill() is used to update memory allocated by > > execmem_alloc(). > > Sigh, I just realized this thread made through linux-mm@xxxxxxxxx, but got > dropped by bpf@xxxxxxxxxxxxxxx, so I guess I will have to resend v3. I don't know what is going on with the bpf list but whatever it is, is silly. You should Cc the right folks to ensure proper review if the bpf list is the issue. > Currently, I have got the following action items for v3: > 1. Add unify API to allocate text memory to motivation; > 2. Update Documentation/x86/x86_64/mm.rst; > 3. Allow none PMD_SIZE allocation for powerpc. - I am really exausted of asking again for real performance tests, you keep saying you can't and I keep saying you can, you are not trying hard enough. Stop thinking about your internal benchmark which you cannot publish. There should be enough crap out which you can use. - A new selftest or set of selftests which demonstrates gain in performance - Extensions maybe of lib/test_vmalloc.c or whatever is appropriate to test correctness - Enhance commit logs to justify the *why*, one of which to hightight is providing an API for memory semantics for special memory pages Luis
