Do not overwrite nr_zones on !NUMA when initialising zlcache_ptr
The non-NUMA case of build_zonelist_cache() would initialize the zlcache_ptr for both node_zonelists[] to NULL. Which is problematic, since non-NUMA only has a single node_zonelists[] entry, and trying to zero the non-existent second one just overwrote the nr_zones field instead. As kswapd uses this value to determine what reclaim work is necessary, the result is that kswapd never reclaims. This causes processes to stall frequently in low-memory situations as they always direct reclaim. This patch initialises zlcache_ptr correctly. Signed-off-by: Mel Gorman <mel@csn.ul.ie> Tested-by: Dan Williams <dan.j.williams@intel.com> [ Simplified patch a bit ] Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
c461a97311
commit
494de90098
|
@ -2328,7 +2328,6 @@ static void build_zonelists(pg_data_t *pgdat)
|
|||
static void build_zonelist_cache(pg_data_t *pgdat)
|
||||
{
|
||||
pgdat->node_zonelists[0].zlcache_ptr = NULL;
|
||||
pgdat->node_zonelists[1].zlcache_ptr = NULL;
|
||||
}
|
||||
|
||||
#endif /* CONFIG_NUMA */
|
||||
|
|
Loading…
Reference in New Issue