On Fri, May 19, 2023 at 11:29:45AM +0300, Mike Rapoport wrote: > Your allocator implicitly relies on vmalloc because of module_alloc ;-) > > What I was thinking is that we can replace module_alloc() calls in your > allocator with something based on my unmapped_alloc(). If we make the part > that refills the cache also take care of creating the mapping in the > module address space, that should cover everything. Yeah, that's exactly what I was thinking :) Liam was also just mentioning on IRC vmalloc lock contention came up again at LSF, and that's historically always been an isuse - going with your patchset for the backend nicely avoids that. If I have time (hah! big if :) I'll see if I can cook up a patchset that combines our two approaches over the weekend.
