Re: [PATCH v4 bpf 0/4] vmalloc: bpf: introduce VM_ALLOW_HUGE_VMAP

From: Christoph Hellwig
Date: Sat Apr 16 2022 - 01:09:00 EST

Next message: kernel test robot: "[jolsa-perf:bpf/fixes 1/4] do_mounts.c:(.text+0x5): multiple definition of `kallsyms_lookup_names'; init/main.o:main.c:(.text+0x32): first defined here"
Previous message: Bart Van Assche: "Re: [PATCH v4 1/1] scsi: Fix racing between dev init and dev reset"
Next in thread: Song Liu: "Re: [PATCH v4 bpf 0/4] vmalloc: bpf: introduce VM_ALLOW_HUGE_VMAP"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Fri, Apr 15, 2022 at 12:05:42PM -0700, Luis Chamberlain wrote:
> Looks good except for that I think this should just wait for v5.19. The
> fixes are so large I can't see why this needs to be rushed in other than
> the first assumptions of the optimizations had some flaws addressed here.

Patches 1 and 2 are bug fixes for regressions caused by using huge page
backed vmalloc by default. So I think we do need it for 5.18. The
other two do look like candidates for 5.19, though.

Next message: kernel test robot: "[jolsa-perf:bpf/fixes 1/4] do_mounts.c:(.text+0x5): multiple definition of `kallsyms_lookup_names'; init/main.o:main.c:(.text+0x32): first defined here"
Previous message: Bart Van Assche: "Re: [PATCH v4 1/1] scsi: Fix racing between dev init and dev reset"
Next in thread: Song Liu: "Re: [PATCH v4 bpf 0/4] vmalloc: bpf: introduce VM_ALLOW_HUGE_VMAP"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]