On 2024/2/24 00:41, Vlastimil Babka wrote: > On 2/22/24 03:32, Chengming Zhou wrote: >> On 2024/2/22 09:10, Song, Xiongwei wrote: >>> Hi Vlastimil, >>> >>>> On Tue, Feb 20, 2024 at 05:58:25PM +0100, Vlastimil Babka wrote: >>>> 0;95;0c> The SLAB_MEM_SPREAD flag used to be implemented in SLAB, which was >>>>> removed. SLUB instead relies on the page allocator's NUMA policies. >>>>> Change the flag's value to 0 to free up the value it had, and mark it >>>>> for full removal once all users are gone. >>>>> >>>>> Reported-by: Steven Rostedt <rostedt@xxxxxxxxxxx> >>>>> Closes: https://lore.kernel.org/all/20240131172027.10f64405@xxxxxxxxxxxxxxxxxx/ >>>>> Signed-off-by: Vlastimil Babka <vbabka@xxxxxxx> >>>> >>>> Reviewed-by: Roman Gushchin <roman.gushchin@xxxxxxxxx> >>>> >>>> Do you plan to follow up with a patch series removing all usages? >>> >>> If you are not available with it, I can do. >> >> Actually, I have done it yesterday. Sorry, I just forgot this task. :) >> >> I plan to send out it after this series merged in the slab branch. And >> I'm wondering is it better to put all diffs in one huge patch or split >> every diff to each patch? > > I'd suggest you do a patch per subsystem (mostly different filesystems) and > send them out to respective maintainers to pick in their trees. I've talked > to David from btrfs and he suggested this way. Ok, will send out individually. > > You don't need to wait for this series to be merged. The flag is already a > no-op as of 6.8-rc1. Also I'd suggest sending the patches individually. In a > series they wouldn't depend on each other anyway, and you would either have > to Cc maintainers separately per patch of the series, or everyone on > everything, and there would always be somebody who would prefer the other > way that you pick. Right, thanks for your instructions! > >> Thanks! >
