diff for duplicates of <54F6303C.5080806@suse.cz> diff --git a/a/1.txt b/N1/1.txt index efd3997..3155c4e 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -45,9 +45,3 @@ But I wonder, can we change this even after VM_PINNED is introduced, if existing code depends on "no minor faults in mlocked areas", whatever the docs say? On the other hand, compaction is not the only source of migrations. I wonder what the NUMA balancing does (not) about mlocked areas... - --- -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 d71c8f1..6729a5f 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -68,12 +68,6 @@ "But I wonder, can we change this even after VM_PINNED is introduced, if existing\n" "code depends on \"no minor faults in mlocked areas\", whatever the docs say? On\n" "the other hand, compaction is not the only source of migrations. I wonder what\n" - "the NUMA balancing does (not) about mlocked areas...\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>" + the NUMA balancing does (not) about mlocked areas... -1686b8d2891622c0931745695b0fc92b09ece6294779ff9f1face7fa234ea6f8 +5212a99b31ff061b09dfcca8d03a03108e2c8a777dd0bd98449f3c930075e459
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.