diff for duplicates of <b247e32a-03f0-1dbf-59e5-d7cbf90a5500@arm.com> diff --git a/a/1.txt b/N1/1.txt index 116b33c..6892449 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,5 +1,5 @@ On 27/06/2023 04:04, Yu Zhao wrote: -> On Mon, Jun 26, 2023 at 11:15 AM Ryan Roberts <ryan.roberts@arm.com> wrote: +> On Mon, Jun 26, 2023 at 11:15 AM Ryan Roberts <ryan.roberts@arm.com> wrote: >> >> This allows batching the rmap removal with folio_remove_rmap_range(), >> which means we avoid spuriously adding a partially unmapped folio to the diff --git a/a/content_digest b/N1/content_digest index a89fc0d..8ee92a2 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -25,11 +25,12 @@ linux-alpha@vger.kernel.org linux-arm-kernel@lists.infradead.org linux-ia64@vger.kernel.org - " linux-m68k@lists\0" + linux-m68k@lists.linux-m68k.org + " linux-s390@vger.kernel.org\0" "\00:1\0" "b\0" "On 27/06/2023 04:04, Yu Zhao wrote:\n" - "> On Mon, Jun 26, 2023 at 11:15\303\242\342\202\254\302\257AM Ryan Roberts <ryan.roberts@arm.com> wrote:\n" + "> On Mon, Jun 26, 2023 at 11:15\342\200\257AM Ryan Roberts <ryan.roberts@arm.com> wrote:\n" ">>\n" ">> This allows batching the rmap removal with folio_remove_rmap_range(),\n" ">> which means we avoid spuriously adding a partially unmapped folio to the\n" @@ -58,4 +59,4 @@ "we can drop this as you suggest. If I still see a reasonable perf improvement\n" without it, I'll drop for v2. -32ca01acec21a5a8050c5556469c6dc5329026d75c805e7f19d562bc06b59724 +1bd3a13066de39ee350467f744d3833a5eade74c072bf90ec197c85f87a741f0
diff --git a/a/1.txt b/N2/1.txt index 116b33c..3fa593b 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,5 +1,5 @@ On 27/06/2023 04:04, Yu Zhao wrote: -> On Mon, Jun 26, 2023 at 11:15 AM Ryan Roberts <ryan.roberts@arm.com> wrote: +> On Mon, Jun 26, 2023 at 11:15 AM Ryan Roberts <ryan.roberts@arm.com> wrote: >> >> This allows batching the rmap removal with folio_remove_rmap_range(), >> which means we avoid spuriously adding a partially unmapped folio to the @@ -27,3 +27,8 @@ performance gains. But since then Yin Fengwei's patch to make this more efficient has been accepted so perhaps that solves the problem and in that case we can drop this as you suggest. If I still see a reasonable perf improvement without it, I'll drop for v2. + +_______________________________________________ +linux-arm-kernel mailing list +linux-arm-kernel@lists.infradead.org +http://lists.infradead.org/mailman/listinfo/linux-arm-kernel diff --git a/a/content_digest b/N2/content_digest index a89fc0d..98d327e 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -25,11 +25,12 @@ linux-alpha@vger.kernel.org linux-arm-kernel@lists.infradead.org linux-ia64@vger.kernel.org - " linux-m68k@lists\0" + linux-m68k@lists.linux-m68k.org + " linux-s390@vger.kernel.org\0" "\00:1\0" "b\0" "On 27/06/2023 04:04, Yu Zhao wrote:\n" - "> On Mon, Jun 26, 2023 at 11:15\303\242\342\202\254\302\257AM Ryan Roberts <ryan.roberts@arm.com> wrote:\n" + "> On Mon, Jun 26, 2023 at 11:15\342\200\257AM Ryan Roberts <ryan.roberts@arm.com> wrote:\n" ">>\n" ">> This allows batching the rmap removal with folio_remove_rmap_range(),\n" ">> which means we avoid spuriously adding a partially unmapped folio to the\n" @@ -56,6 +57,11 @@ "performance gains. But since then Yin Fengwei's patch to make this more\n" "efficient has been accepted so perhaps that solves the problem and in that case\n" "we can drop this as you suggest. If I still see a reasonable perf improvement\n" - without it, I'll drop for v2. + "without it, I'll drop for v2.\n" + "\n" + "_______________________________________________\n" + "linux-arm-kernel mailing list\n" + "linux-arm-kernel@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -32ca01acec21a5a8050c5556469c6dc5329026d75c805e7f19d562bc06b59724 +10044831598d3146530f2f9da0ee35d3ec107221af8deecfab4726a3d4cbd08c
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.