diff for duplicates of <562752F0.1020502@suse.cz> diff --git a/a/1.txt b/N1/1.txt index 61dfec9..666f7b3 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -108,7 +108,7 @@ On 10/20/2015 07:58 PM, Jarno Rajahalme wrote: >>>> However, there is still a high likelihood that the memory >>>> allocations would >>>> not share a cache line, which should prevent the nodes from invalidating ->>>> each othera??s caches. Based on this I do not see a problem relaxing the +>>>> each other’s caches. Based on this I do not see a problem relaxing the >>>> memory allocation for the default stats node. If node 0 has memory, >>>> however, >>>> it would be better to allocate the memory from node 0. @@ -129,7 +129,7 @@ On 10/20/2015 07:58 PM, Jarno Rajahalme wrote: >>>> It would still be preferable to know from which node the default >>>> stats node >>>> was allocated, and store it in the appropriate pointer in the array. We ->>>> could then add a new a??default stats node indexa?? that would be used +>>>> could then add a new “default stats node index” that would be used >>>> to locate >>>> the node in the array of pointers we already have. That way we would >>>> avoid @@ -211,9 +211,3 @@ fails to guarantee the node is online? > > Jarno > - --- -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 346d466..f24c5fd 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -136,7 +136,7 @@ ">>>> However, there is still a high likelihood that the memory\n" ">>>> allocations would\n" ">>>> not share a cache line, which should prevent the nodes from invalidating\n" - ">>>> each othera??s caches. Based on this I do not see a problem relaxing the\n" + ">>>> each other\342\200\231s caches. Based on this I do not see a problem relaxing the\n" ">>>> memory allocation for the default stats node. If node 0 has memory,\n" ">>>> however,\n" ">>>> it would be better to allocate the memory from node 0.\n" @@ -157,7 +157,7 @@ ">>>> It would still be preferable to know from which node the default\n" ">>>> stats node\n" ">>>> was allocated, and store it in the appropriate pointer in the array. We\n" - ">>>> could then add a new a??default stats node indexa?? that would be used\n" + ">>>> could then add a new \342\200\234default stats node index\342\200\235 that would be used\n" ">>>> to locate\n" ">>>> the node in the array of pointers we already have. That way we would\n" ">>>> avoid\n" @@ -238,12 +238,6 @@ "> when __GFP_THISNODE is not set?\n" ">\n" "> Jarno\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>" + > -d7b4050dbfd599961b3430ec65e91ddb8222b382759f5bfa975329445649af52 +3515e31f0d2b8754c4d3cbc02b5a22eeb248aace42274ed27e79e6e743502dbe
diff --git a/a/1.txt b/N2/1.txt index 61dfec9..a2f2e25 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -108,7 +108,7 @@ On 10/20/2015 07:58 PM, Jarno Rajahalme wrote: >>>> However, there is still a high likelihood that the memory >>>> allocations would >>>> not share a cache line, which should prevent the nodes from invalidating ->>>> each othera??s caches. Based on this I do not see a problem relaxing the +>>>> each other’s caches. Based on this I do not see a problem relaxing the >>>> memory allocation for the default stats node. If node 0 has memory, >>>> however, >>>> it would be better to allocate the memory from node 0. @@ -129,7 +129,7 @@ On 10/20/2015 07:58 PM, Jarno Rajahalme wrote: >>>> It would still be preferable to know from which node the default >>>> stats node >>>> was allocated, and store it in the appropriate pointer in the array. We ->>>> could then add a new a??default stats node indexa?? that would be used +>>>> could then add a new “default stats node index” that would be used >>>> to locate >>>> the node in the array of pointers we already have. That way we would >>>> avoid diff --git a/a/content_digest b/N2/content_digest index 346d466..d7ec1a6 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -136,7 +136,7 @@ ">>>> However, there is still a high likelihood that the memory\n" ">>>> allocations would\n" ">>>> not share a cache line, which should prevent the nodes from invalidating\n" - ">>>> each othera??s caches. Based on this I do not see a problem relaxing the\n" + ">>>> each other\342\200\231s caches. Based on this I do not see a problem relaxing the\n" ">>>> memory allocation for the default stats node. If node 0 has memory,\n" ">>>> however,\n" ">>>> it would be better to allocate the memory from node 0.\n" @@ -157,7 +157,7 @@ ">>>> It would still be preferable to know from which node the default\n" ">>>> stats node\n" ">>>> was allocated, and store it in the appropriate pointer in the array. We\n" - ">>>> could then add a new a??default stats node indexa?? that would be used\n" + ">>>> could then add a new \342\200\234default stats node index\342\200\235 that would be used\n" ">>>> to locate\n" ">>>> the node in the array of pointers we already have. That way we would\n" ">>>> avoid\n" @@ -246,4 +246,4 @@ "see: http://www.linux-mm.org/ .\n" "Don't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>" -d7b4050dbfd599961b3430ec65e91ddb8222b382759f5bfa975329445649af52 +efd5d3e876c29b2a7095ac55e66765ed755c2aef0b6657f6ff785cd7e813e33d
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.