diff for duplicates of <20200130101710-mutt-send-email-mst@kernel.org> diff --git a/a/1.txt b/N1/1.txt index 9973c50..e6391a3 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -6,13 +6,13 @@ On Thu, Jan 30, 2020 at 04:02:34PM +0100, David Hildenbrand wrote: > > <mailto:david@redhat.com>> wrote: > > > > On 29.01.20 01:22, Tyler Sanderson via Virtualization wrote: -> > > A primary advantage of virtio balloon over other memory reclaim -> > > mechanisms is that it can pressure the guest's page cache into +> > > A primary advantage of virtio balloon over other memory reclaim +> > > mechanisms is that it can pressure the guest's page cache into > > shrinking. > > > > > > However, since the balloon driver changed to using the shrinker API > > > -> > <https://github.com/torvalds/linux/commit/71994620bb25a8b109388fefa9e99a28e355255a#diff-fd202acf694d9eba19c8c64da3e480c9> this +> > <https://github.com/torvalds/linux/commit/71994620bb25a8b109388fefa9e99a28e355255a#diff-fd202acf694d9eba19c8c64da3e480c9> this > > > use case has become a bit more tricky. I'm wondering what the intended > > > device implementation is. > > > @@ -53,7 +53,7 @@ On Thu, Jan 30, 2020 at 04:02:34PM +0100, David Hildenbrand wrote: > > notifier callback, but I'm wondering if the balloon driver could specify > > a "nice" level to the shrinker API that would cause it to be reclaimed > > from only as a last resort? -> >  +> > > > Cc-ing linux-mm, Michal and Michael. diff --git a/a/content_digest b/N1/content_digest index e1e7ee2..fddd609 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -6,11 +6,12 @@ "Subject\0Re: Balloon pressuring page cache\0" "Date\0Thu, 30 Jan 2020 10:20:17 -0500\0" "To\0David Hildenbrand <david@redhat.com>\0" - "Cc\0Michal Hocko <mhocko@kernel.org>" - Tyler Sanderson <tysand@google.com> - linux-mm@kvack.org <linux-mm@kvack.org> + "Cc\0Tyler Sanderson <tysand@google.com>" + virtualization@lists.linux-foundation.org + Wei Wang <wei.w.wang@intel.com> David Rientjes <rientjes@google.com> - " virtualization@lists.linux-foundation.org\0" + linux-mm@kvack.org <linux-mm@kvack.org> + " Michal Hocko <mhocko@kernel.org>\0" "\00:1\0" "b\0" "On Thu, Jan 30, 2020 at 04:02:34PM +0100, David Hildenbrand wrote:\n" @@ -21,13 +22,13 @@ "> > <mailto:david@redhat.com>> wrote:\n" "> > \n" "> > On 29.01.20 01:22, Tyler Sanderson via Virtualization wrote:\n" - "> > > A primary advantage of virtio balloon over other\303\202\302\240memory reclaim\n" - "> > > mechanisms is that it can\303\202\302\240pressure the guest's page cache into\n" + "> > > A primary advantage of virtio balloon over other\302\240memory reclaim\n" + "> > > mechanisms is that it can\302\240pressure the guest's page cache into\n" "> > shrinking.\n" "> > >\n" "> > > However, since the balloon driver changed to using the shrinker API\n" "> > >\n" - "> > <https://github.com/torvalds/linux/commit/71994620bb25a8b109388fefa9e99a28e355255a#diff-fd202acf694d9eba19c8c64da3e480c9>\303\202\302\240this\n" + "> > <https://github.com/torvalds/linux/commit/71994620bb25a8b109388fefa9e99a28e355255a#diff-fd202acf694d9eba19c8c64da3e480c9>\302\240this\n" "> > > use case has become a bit more tricky. I'm wondering what the intended\n" "> > > device implementation is.\n" "> > >\n" @@ -68,7 +69,7 @@ "> > notifier callback, but I'm wondering if the balloon driver could specify\n" "> > a \"nice\" level to the shrinker API that would cause it to be reclaimed\n" "> > from only as a last resort?\n" - "> > \303\202\302\240\n" + "> > \302\240\n" "> \n" "> Cc-ing linux-mm, Michal and Michael.\n" "\n" @@ -89,4 +90,4 @@ "> \n" > David / dhildenb -92b65ed75f094122b1eeb1ab5af1fd7b2880ae6aad4c47f0e56f777cb9237318 +fd7c4ee42eba1cd4524b27694576565252346a8cbe6de48a1cf8d1af7651f345
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.