diff for duplicates of <20100527042332.GH22536@laptop> diff --git a/a/1.txt b/N1/1.txt index a4079d2..4907dca 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -86,9 +86,3 @@ pruning. This isn't the case with icache. I would indeed like to focus on the benefits of the patchset as a whole. Leaving aside the xfs changes, it would be interesting to have at least a few numbers for dcache/icache heavy workloads. - - -_______________________________________________ -xfs mailing list -xfs@oss.sgi.com -http://oss.sgi.com/mailman/listinfo/xfs diff --git a/a/content_digest b/N1/content_digest index 3772a9a..9b8d5df 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -8,9 +8,9 @@ "Subject\0Re: [PATCH 1/5] inode: Make unused inode LRU per superblock\0" "Date\0Thu, 27 May 2010 14:23:32 +1000\0" "To\0Dave Chinner <david@fromorbit.com>\0" - "Cc\0linux-fsdevel@vger.kernel.org" + "Cc\0linux-kernel@vger.kernel.org" + linux-fsdevel@vger.kernel.org linux-mm@kvack.org - linux-kernel@vger.kernel.org " xfs@oss.sgi.com\0" "\00:1\0" "b\0" @@ -101,12 +101,6 @@ "\n" "I would indeed like to focus on the benefits of the patchset as a\n" "whole. Leaving aside the xfs changes, it would be interesting to\n" - "have at least a few numbers for dcache/icache heavy workloads.\n" - "\n" - "\n" - "_______________________________________________\n" - "xfs mailing list\n" - "xfs@oss.sgi.com\n" - http://oss.sgi.com/mailman/listinfo/xfs + have at least a few numbers for dcache/icache heavy workloads. -06d7c07195cbb0f3b458eca404d2004a92047e41fe760f20d5e845eaa1b96dd8 +0909e8b78ce3afed53e8817afecaea7ccc0e8e723a4123cf81b758c16db80400
diff --git a/a/1.txt b/N2/1.txt index a4079d2..df7b2d8 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -88,7 +88,8 @@ whole. Leaving aside the xfs changes, it would be interesting to have at least a few numbers for dcache/icache heavy workloads. -_______________________________________________ -xfs mailing list -xfs@oss.sgi.com -http://oss.sgi.com/mailman/listinfo/xfs +-- +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 3772a9a..7f51d21 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -8,9 +8,9 @@ "Subject\0Re: [PATCH 1/5] inode: Make unused inode LRU per superblock\0" "Date\0Thu, 27 May 2010 14:23:32 +1000\0" "To\0Dave Chinner <david@fromorbit.com>\0" - "Cc\0linux-fsdevel@vger.kernel.org" + "Cc\0linux-kernel@vger.kernel.org" + linux-fsdevel@vger.kernel.org linux-mm@kvack.org - linux-kernel@vger.kernel.org " xfs@oss.sgi.com\0" "\00:1\0" "b\0" @@ -104,9 +104,10 @@ "have at least a few numbers for dcache/icache heavy workloads.\n" "\n" "\n" - "_______________________________________________\n" - "xfs mailing list\n" - "xfs@oss.sgi.com\n" - http://oss.sgi.com/mailman/listinfo/xfs + "--\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>" -06d7c07195cbb0f3b458eca404d2004a92047e41fe760f20d5e845eaa1b96dd8 +1bc57d9fe3c0a924bcefe98ea854bf264ee7d1210557be7b56bdad188d0cc8d2
diff --git a/a/1.txt b/N3/1.txt index a4079d2..f819530 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -20,7 +20,7 @@ On Thu, May 27, 2010 at 02:02:10PM +1000, Dave Chinner wrote: > > > > > > However, the reason for doing this to the inode cache is not for > > > scalability, it's because we have a tight relationship between the -> > > dentry and inode cacheѕ. That is, reclaim from the dentry LRU grows +> > > dentry and inode cacheN?. That is, reclaim from the dentry LRU grows > > > the inode LRU. Like the registration of the shrinkers, this is kind > > > of an implicit, undocumented behavour of the current shrinker > > > implemenation. @@ -88,7 +88,8 @@ whole. Leaving aside the xfs changes, it would be interesting to have at least a few numbers for dcache/icache heavy workloads. -_______________________________________________ -xfs mailing list -xfs@oss.sgi.com -http://oss.sgi.com/mailman/listinfo/xfs +-- +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/N3/content_digest index 3772a9a..1fc3544 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -8,9 +8,9 @@ "Subject\0Re: [PATCH 1/5] inode: Make unused inode LRU per superblock\0" "Date\0Thu, 27 May 2010 14:23:32 +1000\0" "To\0Dave Chinner <david@fromorbit.com>\0" - "Cc\0linux-fsdevel@vger.kernel.org" + "Cc\0linux-kernel@vger.kernel.org" + linux-fsdevel@vger.kernel.org linux-mm@kvack.org - linux-kernel@vger.kernel.org " xfs@oss.sgi.com\0" "\00:1\0" "b\0" @@ -36,7 +36,7 @@ "> > > \n" "> > > However, the reason for doing this to the inode cache is not for\n" "> > > scalability, it's because we have a tight relationship between the\n" - "> > > dentry and inode cache\321\225. That is, reclaim from the dentry LRU grows\n" + "> > > dentry and inode cacheN?. That is, reclaim from the dentry LRU grows\n" "> > > the inode LRU. Like the registration of the shrinkers, this is kind\n" "> > > of an implicit, undocumented behavour of the current shrinker\n" "> > > implemenation.\n" @@ -104,9 +104,10 @@ "have at least a few numbers for dcache/icache heavy workloads.\n" "\n" "\n" - "_______________________________________________\n" - "xfs mailing list\n" - "xfs@oss.sgi.com\n" - http://oss.sgi.com/mailman/listinfo/xfs + "--\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>" -06d7c07195cbb0f3b458eca404d2004a92047e41fe760f20d5e845eaa1b96dd8 +19ead497227848c78c71dc2f6ad8b8ba6a19e378b8094bf82d1fdb1474098ee5
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.