diff for duplicates of <537098fb-f049-482a-97cf-b3695bf2c340@default> diff --git a/a/1.txt b/N1/1.txt index 46b878f..3d07918 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -10,11 +10,11 @@ > JBeulich@novell.com; Kurt Hackel; npiggin@suse.de; Dave Mccracken; > riel@redhat.com; avi@redhat.com; Konrad Wilk > Subject: Re: [PATCH V3 0/8] Cleancache: overview ->=20 +> > On 07/23/2010 08:14 PM, Dan Magenheimer wrote: > >> From: Christoph Hellwig [mailto:hch@infradead.org] ->=20 ->=20 +> +> > >> Also making the ops vector global is just a bad idea. > >> There is nothing making this sort of caching inherently global. > > @@ -25,7 +25,7 @@ > > Do you have a suggestion on how to avoid a global ops > > vector while still serving the needs of both existing > > users? ->=20 +> > Maybe introduce cleancache_register(struct cleancache_ops *ops)? > This will allow making cleancache_ops non-global. No value add > but maybe that's cleaner? diff --git a/a/content_digest b/N1/content_digest index 3c82aa3..8e71e45 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -44,11 +44,11 @@ "> JBeulich@novell.com; Kurt Hackel; npiggin@suse.de; Dave Mccracken;\n" "> riel@redhat.com; avi@redhat.com; Konrad Wilk\n" "> Subject: Re: [PATCH V3 0/8] Cleancache: overview\n" - ">=20\n" + "> \n" "> On 07/23/2010 08:14 PM, Dan Magenheimer wrote:\n" "> >> From: Christoph Hellwig [mailto:hch@infradead.org]\n" - ">=20\n" - ">=20\n" + "> \n" + "> \n" "> >> Also making the ops vector global is just a bad idea.\n" "> >> There is nothing making this sort of caching inherently global.\n" "> >\n" @@ -59,7 +59,7 @@ "> > Do you have a suggestion on how to avoid a global ops\n" "> > vector while still serving the needs of both existing\n" "> > users?\n" - ">=20\n" + "> \n" "> Maybe introduce cleancache_register(struct cleancache_ops *ops)?\n" "> This will allow making cleancache_ops non-global. No value add\n" "> but maybe that's cleaner?\n" @@ -74,4 +74,4 @@ "see: http://www.linux-mm.org/ .\n" "Don't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>" -b38662164d5d8864e6795376f8c6962831507459b0f551e59fa89a89fda527ee +1b35cbef9dca18b0a0c87d9f2b426dc1937280612142542253f20a46cd3feb4f
diff --git a/a/1.txt b/N2/1.txt index 46b878f..1263671 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,20 +1,20 @@ -> From: Nitin Gupta [mailto:ngupta@vflare.org] +> From: Nitin Gupta [mailto:ngupta at vflare.org] > Sent: Friday, July 23, 2010 9:05 AM > To: Dan Magenheimer -> Cc: Christoph Hellwig; akpm@linux-foundation.org; Chris Mason; -> viro@zeniv.linux.org.uk; adilger@sun.com; tytso@mit.edu; -> mfasheh@suse.com; Joel Becker; matthew@wil.cx; linux- -> btrfs@vger.kernel.org; linux-kernel@vger.kernel.org; linux- -> fsdevel@vger.kernel.org; linux-ext4@vger.kernel.org; ocfs2- -> devel@oss.oracle.com; linux-mm@kvack.org; jeremy@goop.org; -> JBeulich@novell.com; Kurt Hackel; npiggin@suse.de; Dave Mccracken; -> riel@redhat.com; avi@redhat.com; Konrad Wilk +> Cc: Christoph Hellwig; akpm at linux-foundation.org; Chris Mason; +> viro at zeniv.linux.org.uk; adilger at sun.com; tytso at mit.edu; +> mfasheh at suse.com; Joel Becker; matthew at wil.cx; linux- +> btrfs at vger.kernel.org; linux-kernel at vger.kernel.org; linux- +> fsdevel at vger.kernel.org; linux-ext4 at vger.kernel.org; ocfs2- +> devel at oss.oracle.com; linux-mm at kvack.org; jeremy at goop.org; +> JBeulich at novell.com; Kurt Hackel; npiggin at suse.de; Dave Mccracken; +> riel at redhat.com; avi at redhat.com; Konrad Wilk > Subject: Re: [PATCH V3 0/8] Cleancache: overview ->=20 +> > On 07/23/2010 08:14 PM, Dan Magenheimer wrote: -> >> From: Christoph Hellwig [mailto:hch@infradead.org] ->=20 ->=20 +> >> From: Christoph Hellwig [mailto:hch at infradead.org] +> +> > >> Also making the ops vector global is just a bad idea. > >> There is nothing making this sort of caching inherently global. > > @@ -25,7 +25,7 @@ > > Do you have a suggestion on how to avoid a global ops > > vector while still serving the needs of both existing > > users? ->=20 +> > Maybe introduce cleancache_register(struct cleancache_ops *ops)? > This will allow making cleancache_ops non-global. No value add > but maybe that's cleaner? @@ -33,9 +33,3 @@ Oh, OK, that seems reasonable. Dan - --- -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 3c82aa3..c3bafb1 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -4,7 +4,7 @@ "ref\0364c83bd-ccb2-48cc-920d-ffcf9ca7df19@default 4C49AFAE.1070300@vflare.org\0" "ref\04C49AFAE.1070300@vflare.org\0" "From\0Dan Magenheimer <dan.magenheimer@oracle.com>\0" - "Subject\0RE: [PATCH V3 0/8] Cleancache: overview\0" + "Subject\0[Ocfs2-devel] [PATCH V3 0/8] Cleancache: overview\0" "Date\0Fri, 23 Jul 2010 10:43:17 -0700 (PDT)\0" "To\0ngupta@vflare.org\0" "Cc\0Christoph Hellwig <hch@infradead.org>" @@ -32,23 +32,23 @@ " Konrad Wilk <konrad.wilk@oracle.com>\0" "\00:1\0" "b\0" - "> From: Nitin Gupta [mailto:ngupta@vflare.org]\n" + "> From: Nitin Gupta [mailto:ngupta at vflare.org]\n" "> Sent: Friday, July 23, 2010 9:05 AM\n" "> To: Dan Magenheimer\n" - "> Cc: Christoph Hellwig; akpm@linux-foundation.org; Chris Mason;\n" - "> viro@zeniv.linux.org.uk; adilger@sun.com; tytso@mit.edu;\n" - "> mfasheh@suse.com; Joel Becker; matthew@wil.cx; linux-\n" - "> btrfs@vger.kernel.org; linux-kernel@vger.kernel.org; linux-\n" - "> fsdevel@vger.kernel.org; linux-ext4@vger.kernel.org; ocfs2-\n" - "> devel@oss.oracle.com; linux-mm@kvack.org; jeremy@goop.org;\n" - "> JBeulich@novell.com; Kurt Hackel; npiggin@suse.de; Dave Mccracken;\n" - "> riel@redhat.com; avi@redhat.com; Konrad Wilk\n" + "> Cc: Christoph Hellwig; akpm at linux-foundation.org; Chris Mason;\n" + "> viro at zeniv.linux.org.uk; adilger at sun.com; tytso at mit.edu;\n" + "> mfasheh at suse.com; Joel Becker; matthew at wil.cx; linux-\n" + "> btrfs at vger.kernel.org; linux-kernel at vger.kernel.org; linux-\n" + "> fsdevel at vger.kernel.org; linux-ext4 at vger.kernel.org; ocfs2-\n" + "> devel at oss.oracle.com; linux-mm at kvack.org; jeremy at goop.org;\n" + "> JBeulich at novell.com; Kurt Hackel; npiggin at suse.de; Dave Mccracken;\n" + "> riel at redhat.com; avi at redhat.com; Konrad Wilk\n" "> Subject: Re: [PATCH V3 0/8] Cleancache: overview\n" - ">=20\n" + "> \n" "> On 07/23/2010 08:14 PM, Dan Magenheimer wrote:\n" - "> >> From: Christoph Hellwig [mailto:hch@infradead.org]\n" - ">=20\n" - ">=20\n" + "> >> From: Christoph Hellwig [mailto:hch at infradead.org]\n" + "> \n" + "> \n" "> >> Also making the ops vector global is just a bad idea.\n" "> >> There is nothing making this sort of caching inherently global.\n" "> >\n" @@ -59,19 +59,13 @@ "> > Do you have a suggestion on how to avoid a global ops\n" "> > vector while still serving the needs of both existing\n" "> > users?\n" - ">=20\n" + "> \n" "> Maybe introduce cleancache_register(struct cleancache_ops *ops)?\n" "> This will allow making cleancache_ops non-global. No value add\n" "> but maybe that's cleaner?\n" "\n" "Oh, OK, that seems reasonable.\n" "\n" - "Dan\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>" + Dan -b38662164d5d8864e6795376f8c6962831507459b0f551e59fa89a89fda527ee +74876a8da50f56a013c318b09fe83790be35837ca936b772a92201e8dd3b1769
diff --git a/a/1.txt b/N3/1.txt index 46b878f..e463067 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -10,11 +10,11 @@ > JBeulich@novell.com; Kurt Hackel; npiggin@suse.de; Dave Mccracken; > riel@redhat.com; avi@redhat.com; Konrad Wilk > Subject: Re: [PATCH V3 0/8] Cleancache: overview ->=20 +> > On 07/23/2010 08:14 PM, Dan Magenheimer wrote: > >> From: Christoph Hellwig [mailto:hch@infradead.org] ->=20 ->=20 +> +> > >> Also making the ops vector global is just a bad idea. > >> There is nothing making this sort of caching inherently global. > > @@ -25,7 +25,7 @@ > > Do you have a suggestion on how to avoid a global ops > > vector while still serving the needs of both existing > > users? ->=20 +> > Maybe introduce cleancache_register(struct cleancache_ops *ops)? > This will allow making cleancache_ops non-global. No value add > but maybe that's cleaner? @@ -33,9 +33,3 @@ Oh, OK, that seems reasonable. Dan - --- -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 3c82aa3..a229941 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -44,11 +44,11 @@ "> JBeulich@novell.com; Kurt Hackel; npiggin@suse.de; Dave Mccracken;\n" "> riel@redhat.com; avi@redhat.com; Konrad Wilk\n" "> Subject: Re: [PATCH V3 0/8] Cleancache: overview\n" - ">=20\n" + "> \n" "> On 07/23/2010 08:14 PM, Dan Magenheimer wrote:\n" "> >> From: Christoph Hellwig [mailto:hch@infradead.org]\n" - ">=20\n" - ">=20\n" + "> \n" + "> \n" "> >> Also making the ops vector global is just a bad idea.\n" "> >> There is nothing making this sort of caching inherently global.\n" "> >\n" @@ -59,19 +59,13 @@ "> > Do you have a suggestion on how to avoid a global ops\n" "> > vector while still serving the needs of both existing\n" "> > users?\n" - ">=20\n" + "> \n" "> Maybe introduce cleancache_register(struct cleancache_ops *ops)?\n" "> This will allow making cleancache_ops non-global. No value add\n" "> but maybe that's cleaner?\n" "\n" "Oh, OK, that seems reasonable.\n" "\n" - "Dan\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>" + Dan -b38662164d5d8864e6795376f8c6962831507459b0f551e59fa89a89fda527ee +d0963b70d968cbbaaa4c5e2795c4668e5a1f77eee1915775053d223d76a70f30
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.