# HG changeset patch
# User shade
# Date 1567419021 -7200
# Node ID 42a13b4e9553bf2ef4f1b914b44d0ecaaebe1d60
# Parent  47ce198d5cf116f4b9bd0dc6018e2981fddc9c3d
8230425: Shenandoah forces +UseNUMAInterleaving even after explicitly disabled
Reviewed-by: rkennke

diff -r 47ce198d5cf1 -r 42a13b4e9553 src/hotspot/share/gc/shenandoah/shenandoahArguments.cpp
--- a/src/hotspot/share/gc/shenandoah/shenandoahArguments.cpp	Mon Sep 02 11:31:12 2019 +0200
+++ b/src/hotspot/share/gc/shenandoah/shenandoahArguments.cpp	Mon Sep 02 12:10:21 2019 +0200
@@ -60,11 +60,9 @@
   }
 
   // Enable NUMA by default. While Shenandoah is not NUMA-aware, enabling NUMA makes
-  // storage allocation code NUMA-aware, and NUMA interleaving makes the storage
-  // allocated in consistent manner (interleaving) to minimize run-to-run variance.
+  // storage allocation code NUMA-aware.
   if (FLAG_IS_DEFAULT(UseNUMA)) {
     FLAG_SET_DEFAULT(UseNUMA, true);
-    FLAG_SET_DEFAULT(UseNUMAInterleaving, true);
   }
 
   // Set up default number of concurrent threads. We want to have cycles complete fast