diff for duplicates of <20100624000246.GQ6590@dastard> diff --git a/a/1.txt b/N1/1.txt index f8ff4b2..159d84c 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -105,3 +105,9 @@ Dave. -- Dave Chinner david@fromorbit.com + +-- +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 e7ea976..aaa4422 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -120,6 +120,12 @@ "Dave.\n" "-- \n" "Dave Chinner\n" - david@fromorbit.com + "david@fromorbit.com\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>" -2790252439e8ba6ad74efae28d9e7972808b02353285bc54cec58968014fd909 +9e0693d5d48d2e74bb2d2fc6cab6aa55b9a4cfc22621c15bae8e08a6aba5694f
diff --git a/a/1.txt b/N2/1.txt index f8ff4b2..5a6b77a 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -3,9 +3,9 @@ On Mon, Jun 21, 2010 at 10:09:24AM -0700, Michael Rubin wrote: > > On Sun, Jun 20, 2010 at 4:10 PM, Dave Chinner <david@fromorbit.com> wrote: > >> Michael Rubin (3): -> >> writeback: Creating /sys/kernel/mm/writeback/writeback -> >> writeback: per bdi monitoring -> >> writeback: tracking subsystems causing writeback +> >> A writeback: Creating /sys/kernel/mm/writeback/writeback +> >> A writeback: per bdi monitoring +> >> A writeback: tracking subsystems causing writeback > > > > I'm not sure we want to export statistics that represent internal > > implementation details into a fixed userspace API. Who, other than @@ -14,14 +14,14 @@ On Mon, Jun 21, 2010 at 10:09:24AM -0700, Michael Rubin wrote: > > I think there are varying degrees of internal exposure on the patches. > -> >> writeback: Creating /sys/kernel/mm/writeback/writeback +> >> A writeback: Creating /sys/kernel/mm/writeback/writeback > This one seems to not expose any new internals. We already expose the > concept of "dirty", "writeback" and thresholds in /proc/meminfo. I don't see any probems with these stats - no matter the implementation, they'll still be relevant. -> >> writeback: per bdi monitoring +> >>A writeback: per bdi monitoring > > Looking at it again. I think this one is somewhat of a mixed bag. > BDIReclaimable, BdiWriteback, and the dirty thresholds seems safe to @@ -32,7 +32,7 @@ I'd much prefer all the bdi stats in the one spot. It's hard enough to find what you're looking for without splitting them into multiple locations. -The other thing to consider is that tracing requires debugfѕ to be +The other thing to consider is that tracing requires debugfN? to be mounted. Hence most kernels are going to have the debug stats available, anyway.... @@ -105,3 +105,9 @@ Dave. -- Dave Chinner david@fromorbit.com + +-- +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/N2/content_digest index e7ea976..617044d 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -19,9 +19,9 @@ "> \n" "> On Sun, Jun 20, 2010 at 4:10 PM, Dave Chinner <david@fromorbit.com> wrote:\n" "> >> Michael Rubin (3):\n" - "> >> \302\240 writeback: Creating /sys/kernel/mm/writeback/writeback\n" - "> >> \302\240 writeback: per bdi monitoring\n" - "> >> \302\240 writeback: tracking subsystems causing writeback\n" + "> >> A writeback: Creating /sys/kernel/mm/writeback/writeback\n" + "> >> A writeback: per bdi monitoring\n" + "> >> A writeback: tracking subsystems causing writeback\n" "> >\n" "> > I'm not sure we want to export statistics that represent internal\n" "> > implementation details into a fixed userspace API. Who, other than\n" @@ -30,14 +30,14 @@ "> \n" "> I think there are varying degrees of internal exposure on the patches.\n" "> \n" - "> >> \302\240 writeback: Creating /sys/kernel/mm/writeback/writeback\n" + "> >> A writeback: Creating /sys/kernel/mm/writeback/writeback\n" "> This one seems to not expose any new internals. We already expose the\n" "> concept of \"dirty\", \"writeback\" and thresholds in /proc/meminfo.\n" "\n" "I don't see any probems with these stats - no matter the\n" "implementation, they'll still be relevant.\n" "\n" - "> >>\302\240 writeback: per bdi monitoring\n" + "> >>A writeback: per bdi monitoring\n" "> \n" "> Looking at it again. I think this one is somewhat of a mixed bag.\n" "> BDIReclaimable, BdiWriteback, and the dirty thresholds seems safe to\n" @@ -48,7 +48,7 @@ "to find what you're looking for without splitting them into multiple\n" "locations.\n" "\n" - "The other thing to consider is that tracing requires debugf\321\225 to be\n" + "The other thing to consider is that tracing requires debugfN? to be\n" "mounted. Hence most kernels are going to have the debug stats\n" "available, anyway....\n" "\n" @@ -120,6 +120,12 @@ "Dave.\n" "-- \n" "Dave Chinner\n" - david@fromorbit.com + "david@fromorbit.com\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>" -2790252439e8ba6ad74efae28d9e7972808b02353285bc54cec58968014fd909 +860b058f1f0f53a76df9a3ecd16e1df4789fbea4a89bb6ce2ed466de18b34a92
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.