diff for duplicates of <50B403CA.501@jp.fujitsu.com> diff --git a/a/1.txt b/N1/1.txt index 6830e3c..3bf1bd6 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -23,7 +23,7 @@ > -mm tree but I will send a backport to 3.2 in the reply as well) > --- > From 7796f942d62081ad45726efd90b5292b80e7c690 Mon Sep 17 00:00:00 2001 -> From: Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org> +> From: Michal Hocko <mhocko@suse.cz> > Date: Mon, 26 Nov 2012 11:47:57 +0100 > Subject: [PATCH] memcg: do not trigger OOM from add_to_page_cache_locked > @@ -86,11 +86,11 @@ > any reclaim on __GFP_NORETRY doesn't make much sense anyway because this > is effectively a busy loop with allowed OOM in this path. > -> Reported-by: azurIt <azurit-Rm0zKEqwvD4@public.gmane.org> -> Signed-off-by: Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org> +> Reported-by: azurIt <azurit@pobox.sk> +> Signed-off-by: Michal Hocko <mhocko@suse.cz> As a short term fix, I think this patch will work enough and seems simple enough. -Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org> +Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> Reading discussion between you and Johannes, to release locks, I understand the memcg need to return "RETRY" for a long term fix. Thinking a little, @@ -194,3 +194,10 @@ Thank you. > > if (PageTransHuge(page)) { > + + +-- +To unsubscribe, send a message with 'unsubscribe linux-mm' in +the body to majordomo@kvack.org. For more info on Linux MM, +see: http://www.linux-mm.org/ . +Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a> diff --git a/a/content_digest b/N1/content_digest index d182cf8..4411444 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -9,16 +9,15 @@ "ref\020121125135542.GE10623@dhcp22.suse.cz\0" "ref\020121126013855.AF118F5E@pobox.sk\0" "ref\020121126131837.GC17860@dhcp22.suse.cz\0" - "ref\020121126131837.GC17860-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org\0" - "From\0Kamezawa Hiroyuki <kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>\0" + "From\0Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>\0" "Subject\0Re: [PATCH -mm] memcg: do not trigger OOM from add_to_page_cache_locked\0" "Date\0Tue, 27 Nov 2012 09:05:30 +0900\0" - "To\0Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>\0" - "Cc\0azurIt <azurit-Rm0zKEqwvD4@public.gmane.org>" - linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org - linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org - cgroups mailinglist <cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> - " Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>\0" + "To\0Michal Hocko <mhocko@suse.cz>\0" + "Cc\0azurIt <azurit@pobox.sk>" + linux-kernel@vger.kernel.org + linux-mm@kvack.org + cgroups mailinglist <cgroups@vger.kernel.org> + " Johannes Weiner <hannes@cmpxchg.org>\0" "\00:1\0" "b\0" "(2012/11/26 22:18), Michal Hocko wrote:\n" @@ -46,7 +45,7 @@ "> -mm tree but I will send a backport to 3.2 in the reply as well)\n" "> ---\n" "> From 7796f942d62081ad45726efd90b5292b80e7c690 Mon Sep 17 00:00:00 2001\n" - "> From: Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>\n" + "> From: Michal Hocko <mhocko@suse.cz>\n" "> Date: Mon, 26 Nov 2012 11:47:57 +0100\n" "> Subject: [PATCH] memcg: do not trigger OOM from add_to_page_cache_locked\n" ">\n" @@ -109,11 +108,11 @@ "> any reclaim on __GFP_NORETRY doesn't make much sense anyway because this\n" "> is effectively a busy loop with allowed OOM in this path.\n" ">\n" - "> Reported-by: azurIt <azurit-Rm0zKEqwvD4@public.gmane.org>\n" - "> Signed-off-by: Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>\n" + "> Reported-by: azurIt <azurit@pobox.sk>\n" + "> Signed-off-by: Michal Hocko <mhocko@suse.cz>\n" "\n" "As a short term fix, I think this patch will work enough and seems simple enough.\n" - "Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>\n" + "Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>\n" "\n" "Reading discussion between you and Johannes, to release locks, I understand\n" "the memcg need to return \"RETRY\" for a long term fix. Thinking a little,\n" @@ -216,6 +215,13 @@ "> \tint ret;\n" ">\n" "> \tif (PageTransHuge(page)) {\n" - > + ">\n" + "\n" + "\n" + "--\n" + "To unsubscribe, send a message with 'unsubscribe linux-mm' in\n" + "the body to majordomo@kvack.org. For more info on Linux MM,\n" + "see: http://www.linux-mm.org/ .\n" + "Don't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>" -15da7d1d11877d94294217b882b4f82a492cec5c229e46d750e7a26fbe1e44ea +698a89d1cf8d097a60a1894d602b65098a918224e232e36186ac9791566d9a39
diff --git a/a/1.txt b/N2/1.txt index 6830e3c..abf76d9 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -23,7 +23,7 @@ > -mm tree but I will send a backport to 3.2 in the reply as well) > --- > From 7796f942d62081ad45726efd90b5292b80e7c690 Mon Sep 17 00:00:00 2001 -> From: Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org> +> From: Michal Hocko <mhocko@suse.cz> > Date: Mon, 26 Nov 2012 11:47:57 +0100 > Subject: [PATCH] memcg: do not trigger OOM from add_to_page_cache_locked > @@ -86,11 +86,11 @@ > any reclaim on __GFP_NORETRY doesn't make much sense anyway because this > is effectively a busy loop with allowed OOM in this path. > -> Reported-by: azurIt <azurit-Rm0zKEqwvD4@public.gmane.org> -> Signed-off-by: Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org> +> Reported-by: azurIt <azurit@pobox.sk> +> Signed-off-by: Michal Hocko <mhocko@suse.cz> As a short term fix, I think this patch will work enough and seems simple enough. -Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org> +Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> Reading discussion between you and Johannes, to release locks, I understand the memcg need to return "RETRY" for a long term fix. Thinking a little, diff --git a/a/content_digest b/N2/content_digest index d182cf8..0473a22 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -9,16 +9,15 @@ "ref\020121125135542.GE10623@dhcp22.suse.cz\0" "ref\020121126013855.AF118F5E@pobox.sk\0" "ref\020121126131837.GC17860@dhcp22.suse.cz\0" - "ref\020121126131837.GC17860-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org\0" - "From\0Kamezawa Hiroyuki <kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>\0" + "From\0Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>\0" "Subject\0Re: [PATCH -mm] memcg: do not trigger OOM from add_to_page_cache_locked\0" "Date\0Tue, 27 Nov 2012 09:05:30 +0900\0" - "To\0Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>\0" - "Cc\0azurIt <azurit-Rm0zKEqwvD4@public.gmane.org>" - linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org - linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org - cgroups mailinglist <cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> - " Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>\0" + "To\0Michal Hocko <mhocko@suse.cz>\0" + "Cc\0azurIt <azurit@pobox.sk>" + linux-kernel@vger.kernel.org + linux-mm@kvack.org + cgroups mailinglist <cgroups@vger.kernel.org> + " Johannes Weiner <hannes@cmpxchg.org>\0" "\00:1\0" "b\0" "(2012/11/26 22:18), Michal Hocko wrote:\n" @@ -46,7 +45,7 @@ "> -mm tree but I will send a backport to 3.2 in the reply as well)\n" "> ---\n" "> From 7796f942d62081ad45726efd90b5292b80e7c690 Mon Sep 17 00:00:00 2001\n" - "> From: Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>\n" + "> From: Michal Hocko <mhocko@suse.cz>\n" "> Date: Mon, 26 Nov 2012 11:47:57 +0100\n" "> Subject: [PATCH] memcg: do not trigger OOM from add_to_page_cache_locked\n" ">\n" @@ -109,11 +108,11 @@ "> any reclaim on __GFP_NORETRY doesn't make much sense anyway because this\n" "> is effectively a busy loop with allowed OOM in this path.\n" ">\n" - "> Reported-by: azurIt <azurit-Rm0zKEqwvD4@public.gmane.org>\n" - "> Signed-off-by: Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>\n" + "> Reported-by: azurIt <azurit@pobox.sk>\n" + "> Signed-off-by: Michal Hocko <mhocko@suse.cz>\n" "\n" "As a short term fix, I think this patch will work enough and seems simple enough.\n" - "Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>\n" + "Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>\n" "\n" "Reading discussion between you and Johannes, to release locks, I understand\n" "the memcg need to return \"RETRY\" for a long term fix. Thinking a little,\n" @@ -218,4 +217,4 @@ "> \tif (PageTransHuge(page)) {\n" > -15da7d1d11877d94294217b882b4f82a492cec5c229e46d750e7a26fbe1e44ea +e2f654d14da2ce107c68a7361534553c4972d6558c8e39b556e79a6e0750ede5
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.