diff for duplicates of <20040525133543.753fc5a5.davem@redhat.com> diff --git a/a/content_digest b/N1/content_digest index a77110f..f7684aa 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -19,7 +19,8 @@ "Date\0Tue, 25 May 2004 13:35:43 -0700\0" "To\0Linus Torvalds <torvalds@osdl.org>" " wesolows@foobazco.org\0" - "Cc\0willy@debian.org" + "Cc\0wesolows@foobazco.org" + willy@debian.org andrea@suse.de benh@kernel.crashing.org akpm@osdl.org @@ -69,4 +70,4 @@ "all of this stuff. Keith you might want to quote that little \"atomic PTE\n" "update sequence\" piece of code that's in the manual for Linus." -6ce119eb1c2d9924aa0328fd84cc87cbfa9cc9f7605fcf38230c764632975443 +ab208ffcadb26114dca6e00cea62a72a5db7183b136bb9f6ba9b379760c28b13
diff --git a/a/1.txt b/N2/1.txt index dffb028..47fde47 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -6,7 +6,7 @@ Linus Torvalds <torvalds@osdl.org> wrote: > > some kind of loop using the swap instruction? > > Yes. Except that if everybody else uses atomic updates (including the hw -> walkers), _and_ "dirty" is true, then you can optimize that case to just +> walkers), _and_ "dirty" is true, then you can optimize that case to just > to an atomic write (since we don't care what the previous contents were, > and everybody else is guaranteed to honor the fact that we set all the > bits. @@ -36,3 +36,9 @@ previously mentioned we lack a cmpxchg we only have raw SWAP. Keith W. can verify this, he has my old SuperSPARC manual which explains all of this stuff. Keith you might want to quote that little "atomic PTE update sequence" piece of code that's in the manual for Linus. + +-- +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:"aart@kvack.org"> aart@kvack.org </a> diff --git a/a/content_digest b/N2/content_digest index a77110f..c13a2f8 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -38,7 +38,7 @@ "> > some kind of loop using the swap instruction?\n" "> \n" "> Yes. Except that if everybody else uses atomic updates (including the hw \n" - "> walkers), _and_\302\240\"dirty\" is true, then you can optimize that case to just \n" + "> walkers), _and_ \"dirty\" is true, then you can optimize that case to just \n" "> to an atomic write (since we don't care what the previous contents were, \n" "> and everybody else is guaranteed to honor the fact that we set all the \n" "> bits.\n" @@ -67,6 +67,12 @@ "\n" "Keith W. can verify this, he has my old SuperSPARC manual which explains\n" "all of this stuff. Keith you might want to quote that little \"atomic PTE\n" - "update sequence\" piece of code that's in the manual for Linus." + "update sequence\" piece of code that's in the manual for Linus.\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:\"aart@kvack.org\"> aart@kvack.org </a>" -6ce119eb1c2d9924aa0328fd84cc87cbfa9cc9f7605fcf38230c764632975443 +81345b27132af7a4f483f9046bdf54587e01253eb65c7fc6f1bcbc6a763d11d0
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.