diff for duplicates of <1502207168.6577.25.camel@redhat.com> diff --git a/a/1.txt b/N1/1.txt index 9e88d25..c1d319a 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -2,15 +2,15 @@ On Tue, 2017-08-08 at 08:19 -0700, Mike Kravetz wrote: > The other question I was trying to bring up is "What does > MADV_WIPEONFORK -> mean for various types of mappings?"A A For example, if we allow +> mean for various types of mappings?" For example, if we allow > MADV_WIPEONFORK on a file backed mapping what does that mapping look -> like in the child after fork?A A Does it have any connection at all to +> like in the child after fork? Does it have any connection at all to > the -> file?A A Or, do we drop all references to the file and essentially +> file? Or, do we drop all references to the file and essentially > transform -> it to a private (or shared?) anonymous mapping after fork.A A What +> it to a private (or shared?) anonymous mapping after fork. What > about -> System V shared memory?A A What about hugetlb? +> System V shared memory? What about hugetlb? My current patch turns any file-backed VMA into an empty anonymous VMA if MADV_WIPEONFORK was used on that VMA. @@ -28,9 +28,3 @@ be implemented. On the other hand, I am not sure that introducing cases where MADV_WIPEONFORK does not implement wipe-on-fork semantics would reduce user confusion... - --- -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 a196368..332ecc1 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -24,15 +24,15 @@ "\n" "> The other question I was trying to bring up is \"What does\n" "> MADV_WIPEONFORK\n" - "> mean for various types of mappings?\"A A For example, if we allow\n" + "> mean for various types of mappings?\"\302\240\302\240For example, if we allow\n" "> MADV_WIPEONFORK on a file backed mapping what does that mapping look\n" - "> like in the child after fork?A A Does it have any connection at all to\n" + "> like in the child after fork?\302\240\302\240Does it have any connection at all to\n" "> the\n" - "> file?A A Or, do we drop all references to the file and essentially\n" + "> file?\302\240\302\240Or, do we drop all references to the file and essentially\n" "> transform\n" - "> it to a private (or shared?) anonymous mapping after fork.A A What\n" + "> it to a private (or shared?) anonymous mapping after fork.\302\240\302\240What\n" "> about\n" - "> System V shared memory?A A What about hugetlb?\n" + "> System V shared memory?\302\240\302\240What about hugetlb?\n" "\n" "My current patch turns any file-backed VMA into an empty\n" "anonymous VMA if MADV_WIPEONFORK was used on that VMA.\n" @@ -49,12 +49,6 @@ "\n" "On the other hand, I am not sure that introducing cases\n" "where MADV_WIPEONFORK does not implement wipe-on-fork\n" - "semantics would reduce user confusion...\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>" + semantics would reduce user confusion... -e140f7b165b4ae0a3a080deeec7dc392c93df8c5b372d7255e0d9c8c8fe3455a +dbabdb143c8acab02895e5533f09108ab931235a4da2e2ff4cee0c2f500435ec
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.