Re: [v7 PATCH 04/12] mm: vmscan: remove memcg_shrinker_map_size

2021-02-10 Thread Vlastimil Babka
On 2/9/21 9:43 PM, Roman Gushchin wrote: > On Tue, Feb 09, 2021 at 09:46:38AM -0800, Yang Shi wrote: >> Both memcg_shrinker_map_size and shrinker_nr_max is maintained, but actually >> the >> map size can be calculated via shrinker_nr_max, so it seems unnecessary to >> keep both. >> Remove

Re: [v7 PATCH 04/12] mm: vmscan: remove memcg_shrinker_map_size

2021-02-09 Thread Yang Shi
On Tue, Feb 9, 2021 at 12:43 PM Roman Gushchin wrote: > > On Tue, Feb 09, 2021 at 09:46:38AM -0800, Yang Shi wrote: > > Both memcg_shrinker_map_size and shrinker_nr_max is maintained, but > > actually the > > map size can be calculated via shrinker_nr_max, so it seems unnecessary to > > keep

Re: [v7 PATCH 04/12] mm: vmscan: remove memcg_shrinker_map_size

2021-02-09 Thread Roman Gushchin
On Tue, Feb 09, 2021 at 09:46:38AM -0800, Yang Shi wrote: > Both memcg_shrinker_map_size and shrinker_nr_max is maintained, but actually > the > map size can be calculated via shrinker_nr_max, so it seems unnecessary to > keep both. > Remove memcg_shrinker_map_size since shrinker_nr_max is also

[v7 PATCH 04/12] mm: vmscan: remove memcg_shrinker_map_size

2021-02-09 Thread Yang Shi
Both memcg_shrinker_map_size and shrinker_nr_max is maintained, but actually the map size can be calculated via shrinker_nr_max, so it seems unnecessary to keep both. Remove memcg_shrinker_map_size since shrinker_nr_max is also used by iterating the bit map. Acked-by: Kirill Tkhai