All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20200204135533-mutt-send-email-mst@kernel.org>

diff --git a/a/1.txt b/N1/1.txt
index bb194fa..2433cca 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -14,9 +14,9 @@ On Tue, Feb 04, 2020 at 10:52:42AM -0800, Tyler Sanderson wrote:
 >     The issue is that DEFLATE_ON_OOM is under-specified.
 > 
 >     >
->     >  1. It is last-resort, which means the system has already gone through
->     >     heroics to prevent OOM. Those heroic reclaim efforts are expensive
->     >     and impact application performance.
+>     >  1. It is last-resort, which means the system has already gone through
+>     >     heroics to prevent OOM. Those heroic reclaim efforts are expensive
+>     >     and impact application performance.
 > 
 >     That's *exactly* what "deflate on OOM" suggests.
 > 
@@ -42,12 +42,12 @@ new one properly though :)
 >     Under-specified.
 > 
 > 
->     >  2. It lacks understanding of NUMA or other OOM constraints.
+>     >  2. It lacks understanding of NUMA or other OOM constraints.
 > 
 >     Ballooning in general lacks the understanding of NUMA.
 > 
->     >  3. It has a higher potential for bugs due to the subtlety of the
->     >     callback context.
+>     >  3. It has a higher potential for bugs due to the subtlety of the
+>     >     callback context.
 > 
 >     While that is a valid point, it doesn't explain why existing
 >     functionality is changed.
@@ -57,7 +57,7 @@ new one properly though :)
 > 
 > I'm actually not sure how you would safely do memory overcommit without
 > DEFLATE_ON_OOM. So I think it unlocks a huge use case.
->  
+>  
 > 
 > 
 > 
diff --git a/a/content_digest b/N1/content_digest
index 655a328..a86f0db 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -12,12 +12,15 @@
  "Subject\0Re: Balloon pressuring page cache\0"
  "Date\0Tue, 4 Feb 2020 13:56:21 -0500\0"
  "To\0Tyler Sanderson <tysand@google.com>\0"
- "Cc\0virtualization@lists.linux-foundation.org <virtualization@lists.linux-foundation.org>"
-  linux-mm@kvack.org <linux-mm@kvack.org>
-  namit@vmware.com
-  David Rientjes <rientjes@google.com>
+ "Cc\0David Hildenbrand <david@redhat.com>"
   Alexander Duyck <alexander.h.duyck@linux.intel.com>
- " Michal Hocko <mhocko@kernel.org>\0"
+  Wang
+  Wei W <wei.w.wang@intel.com>
+  virtualization@lists.linux-foundation.org <virtualization@lists.linux-foundation.org>
+  David Rientjes <rientjes@google.com>
+  linux-mm@kvack.org <linux-mm@kvack.org>
+  Michal Hocko <mhocko@kernel.org>
+ " namit@vmware.com\0"
  "\00:1\0"
  "b\0"
  "On Tue, Feb 04, 2020 at 10:52:42AM -0800, Tyler Sanderson wrote:\n"
@@ -36,9 +39,9 @@
  ">     The issue is that DEFLATE_ON_OOM is under-specified.\n"
  "> \n"
  ">     >\n"
- ">     >\303\202\302\240 1. It is last-resort, which means the system has already gone through\n"
- ">     >\303\202\302\240 \303\202\302\240 \303\202\302\240heroics to prevent OOM. Those heroic reclaim efforts are expensive\n"
- ">     >\303\202\302\240 \303\202\302\240 \303\202\302\240and impact application performance.\n"
+ ">     >\302\240 1. It is last-resort, which means the system has already gone through\n"
+ ">     >\302\240 \302\240 \302\240heroics to prevent OOM. Those heroic reclaim efforts are expensive\n"
+ ">     >\302\240 \302\240 \302\240and impact application performance.\n"
  "> \n"
  ">     That's *exactly* what \"deflate on OOM\" suggests.\n"
  "> \n"
@@ -64,12 +67,12 @@
  ">     Under-specified.\n"
  "> \n"
  "> \n"
- ">     >\303\202\302\240 2. It lacks understanding of NUMA or other OOM constraints.\n"
+ ">     >\302\240 2. It lacks understanding of NUMA or other OOM constraints.\n"
  "> \n"
  ">     Ballooning in general lacks the understanding of NUMA.\n"
  "> \n"
- ">     >\303\202\302\240 3. It has a higher potential for bugs due to the subtlety\303\202\302\240of the\n"
- ">     >\303\202\302\240 \303\202\302\240 \303\202\302\240callback context.\n"
+ ">     >\302\240 3. It has a higher potential for bugs due to the subtlety\302\240of the\n"
+ ">     >\302\240 \302\240 \302\240callback context.\n"
  "> \n"
  ">     While that is a valid point, it doesn't explain why existing\n"
  ">     functionality is changed.\n"
@@ -79,7 +82,7 @@
  "> \n"
  "> I'm actually not sure how you would safely do memory overcommit without\n"
  "> DEFLATE_ON_OOM. So I think it unlocks a huge use case.\n"
- "> \303\202\302\240\n"
+ "> \302\240\n"
  "> \n"
  "> \n"
  "> \n"
@@ -90,4 +93,4 @@
  "> \n"
  >
 
-42c565a848843b078ae6516bd741bc149df8755c57556ed429a4e4e74f3daf6c
+e7898a3be275d482c5f000257c7e357e8991d9291335736f75ddf32664e6c3c9

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.