Hi Minchan, On Fri, Apr 10, 2020 at 04:11:36PM -0700, Minchan Kim wrote: > It doesn't mean we couldn't use zsmalloc as module any longer. It means > we couldn't use zsmalloc as module with pgtable mapping whcih was little > bit faster on microbenchmark in some architecutre(However, I usually temped > to remove it since it had several problems). However, we could still use > zsmalloc as module as copy way instead of pgtable mapping. Thus, if someone > really want to rollback the feature, they should provide reasonable reason > why it doesn't work for them. "A little fast" wouldn't be enough to exports > deep internal to the module. do you have any data how much faster it is on arm (and does that include arm64 as well)? Besides the exports which were my prime concern, zsmalloc with pgtable mappings also is the only user of map_kernel_range outside of vmalloc.c, if it really is another code base for tiny improvements we could mark map_kernel_range or in fact remove it entirely and open code it in the remaining callers. (unmap_kernel_range is a different story, it has a bunch of callers, and most look odd)
