All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20170324070428.GA7258@aaronlu.sh.intel.com>

diff --git a/a/1.txt b/N1/1.txt
index 8327bd9..09b992c 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -2,12 +2,12 @@ On Tue, Mar 21, 2017 at 07:54:37AM -0700, Dave Hansen wrote:
 > On 03/16/2017 02:07 AM, Michal Hocko wrote:
 > > On Wed 15-03-17 14:38:34, Tim Chen wrote:
 > >> max_active:   time
-> >> 1             8.9s   +-0.5%
-> >> 2             5.65s  +-5.5%
-> >> 4             4.84s  +-0.16%
-> >> 8             4.77s  +-0.97%
-> >> 16            4.85s  +-0.77%
-> >> 32            6.21s  +-0.46%
+> >> 1             8.9s   ±0.5%
+> >> 2             5.65s  ±5.5%
+> >> 4             4.84s  ±0.16%
+> >> 8             4.77s  ±0.97%
+> >> 16            4.85s  ±0.77%
+> >> 32            6.21s  ±0.46%
 > > 
 > > OK, but this will depend on the HW, right? Also now that I am looking at
 > > those numbers more closely. This was about unmapping 320GB area and
@@ -41,7 +41,7 @@ this way, each kworker should be working on a different node.
 
 With this change, time to free the 321G memory is reduced to:
 
-	3.23s +-13.7%  (about 70% decrease)
+	3.23s ±13.7%  (about 70% decrease)
 
 Lock contention is 1.81%:
 
diff --git a/a/content_digest b/N1/content_digest
index cd4fa86..c979654 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -22,12 +22,12 @@
  "> On 03/16/2017 02:07 AM, Michal Hocko wrote:\n"
  "> > On Wed 15-03-17 14:38:34, Tim Chen wrote:\n"
  "> >> max_active:   time\n"
- "> >> 1             8.9s   +-0.5%\n"
- "> >> 2             5.65s  +-5.5%\n"
- "> >> 4             4.84s  +-0.16%\n"
- "> >> 8             4.77s  +-0.97%\n"
- "> >> 16            4.85s  +-0.77%\n"
- "> >> 32            6.21s  +-0.46%\n"
+ "> >> 1             8.9s   \302\2610.5%\n"
+ "> >> 2             5.65s  \302\2615.5%\n"
+ "> >> 4             4.84s  \302\2610.16%\n"
+ "> >> 8             4.77s  \302\2610.97%\n"
+ "> >> 16            4.85s  \302\2610.77%\n"
+ "> >> 32            6.21s  \302\2610.46%\n"
  "> > \n"
  "> > OK, but this will depend on the HW, right? Also now that I am looking at\n"
  "> > those numbers more closely. This was about unmapping 320GB area and\n"
@@ -61,7 +61,7 @@
  "\n"
  "With this change, time to free the 321G memory is reduced to:\n"
  "\n"
- "\t3.23s +-13.7%  (about 70% decrease)\n"
+ "\t3.23s \302\26113.7%  (about 70% decrease)\n"
  "\n"
  "Lock contention is 1.81%:\n"
  "\n"
@@ -182,4 +182,4 @@
  "\treturn 0;\n"
  }
 
-95a56f4f0437d18c937eadf5c0b616860bd8500f04ff77ba4e353df838d1af9f
+316c3fc55a2e5d0e02b1d38179747898857d21b590169985910d4374e0d93b22

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.