diff for duplicates of <4E0B60DE.50908@oracle.com> diff --git a/a/1.txt b/N1/1.txt index d89f0f9..2215a99 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,11 +1,9 @@ -On 06/29/2011 03:42 AM, P=E1draig Brady wrote: +On 06/29/2011 03:42 AM, Pádraig Brady wrote: > There is the argument, that if this interface can distinguish -> these dirty unwritten extents, then why can't the fiemap interface to= -o? +> these dirty unwritten extents, then why can't the fiemap interface too? > The advantage of the fiemap interface is that it can distinguish > empty extents vs holes. Empty extents will become increasingly common -> I think, given the fragmentation and space guarantee benefits they gi= -ve. +> I think, given the fragmentation and space guarantee benefits they give. > It would be cool for cp for example to be able to efficiently copy > empty extents from source to dest. @@ -13,11 +11,10 @@ I'm not too sure about that. Atleast not enabled by default. Most users use cp to backup data. Not empty space. In this case, this empty extent may not even be de-dupable. -=46rankly I'd be happier of cp started to exploited fallocate() to crea= -te larger +Frankly I'd be happier of cp started to exploited fallocate() to create larger extents before copying data into them. Atleast for the large files. --- -To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= -" in -the body of a message to majordomo@vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html + +_______________________________________________ +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 b35a544..de1172d 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -7,24 +7,21 @@ "Subject\0Re: [PATCH] xfstests 255: add a seek_data/seek_hole tester\0" "Date\0Wed, 29 Jun 2011 10:29:02 -0700\0" "To\0P\303\241draig Brady <P@draigbrady.com>\0" - "Cc\0Christoph Hellwig <hch@infradead.org>" - Dave Chinner <david@fromorbit.com> - Josef Bacik <josef@redhat.com> - linux-fsdevel@vger.kernel.org - viro@zeniv.linux.org.uk + "Cc\0linux-btrfs@vger.kernel.org" linux-kernel@vger.kernel.org - linux-btrfs@vger.kernel.org - " xfs@oss.sgi.com\0" + xfs@oss.sgi.com + Christoph Hellwig <hch@infradead.org> + viro@zeniv.linux.org.uk + linux-fsdevel@vger.kernel.org + " Josef Bacik <josef@redhat.com>\0" "\00:1\0" "b\0" - "On 06/29/2011 03:42 AM, P=E1draig Brady wrote:\n" + "On 06/29/2011 03:42 AM, P\303\241draig Brady wrote:\n" "> There is the argument, that if this interface can distinguish\n" - "> these dirty unwritten extents, then why can't the fiemap interface to=\n" - "o?\n" + "> these dirty unwritten extents, then why can't the fiemap interface too?\n" "> The advantage of the fiemap interface is that it can distinguish\n" "> empty extents vs holes. Empty extents will become increasingly common\n" - "> I think, given the fragmentation and space guarantee benefits they gi=\n" - "ve.\n" + "> I think, given the fragmentation and space guarantee benefits they give.\n" "> It would be cool for cp for example to be able to efficiently copy\n" "> empty extents from source to dest.\n" "\n" @@ -32,13 +29,12 @@ "use cp to backup data. Not empty space. In this case, this empty extent\n" "may not even be de-dupable.\n" "\n" - "=46rankly I'd be happier of cp started to exploited fallocate() to crea=\n" - "te larger\n" + "Frankly I'd be happier of cp started to exploited fallocate() to create larger\n" "extents before copying data into them. Atleast for the large files.\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-fsdevel=\n" - "\" in\n" - "the body of a message to majordomo@vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + "\n" + "_______________________________________________\n" + "xfs mailing list\n" + "xfs@oss.sgi.com\n" + http://oss.sgi.com/mailman/listinfo/xfs -0883322c7e59e718e9109c3f22939c5854c12559c3a59082f78defe466e4a5c7 +7effd3a7b91f43a8126889606742445bdd4aa3cd65d29d17934507b678feda16
diff --git a/a/1.txt b/N2/1.txt index d89f0f9..dc33f36 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,11 +1,9 @@ -On 06/29/2011 03:42 AM, P=E1draig Brady wrote: +On 06/29/2011 03:42 AM, Pádraig Brady wrote: > There is the argument, that if this interface can distinguish -> these dirty unwritten extents, then why can't the fiemap interface to= -o? +> these dirty unwritten extents, then why can't the fiemap interface too? > The advantage of the fiemap interface is that it can distinguish > empty extents vs holes. Empty extents will become increasingly common -> I think, given the fragmentation and space guarantee benefits they gi= -ve. +> I think, given the fragmentation and space guarantee benefits they give. > It would be cool for cp for example to be able to efficiently copy > empty extents from source to dest. @@ -13,11 +11,5 @@ I'm not too sure about that. Atleast not enabled by default. Most users use cp to backup data. Not empty space. In this case, this empty extent may not even be de-dupable. -=46rankly I'd be happier of cp started to exploited fallocate() to crea= -te larger +Frankly I'd be happier of cp started to exploited fallocate() to create larger extents before copying data into them. Atleast for the large files. --- -To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= -" in -the body of a message to majordomo@vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N2/content_digest index b35a544..6bb5bbd 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -17,14 +17,12 @@ " xfs@oss.sgi.com\0" "\00:1\0" "b\0" - "On 06/29/2011 03:42 AM, P=E1draig Brady wrote:\n" + "On 06/29/2011 03:42 AM, P\303\241draig Brady wrote:\n" "> There is the argument, that if this interface can distinguish\n" - "> these dirty unwritten extents, then why can't the fiemap interface to=\n" - "o?\n" + "> these dirty unwritten extents, then why can't the fiemap interface too?\n" "> The advantage of the fiemap interface is that it can distinguish\n" "> empty extents vs holes. Empty extents will become increasingly common\n" - "> I think, given the fragmentation and space guarantee benefits they gi=\n" - "ve.\n" + "> I think, given the fragmentation and space guarantee benefits they give.\n" "> It would be cool for cp for example to be able to efficiently copy\n" "> empty extents from source to dest.\n" "\n" @@ -32,13 +30,7 @@ "use cp to backup data. Not empty space. In this case, this empty extent\n" "may not even be de-dupable.\n" "\n" - "=46rankly I'd be happier of cp started to exploited fallocate() to crea=\n" - "te larger\n" - "extents before copying data into them. Atleast for the large files.\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-fsdevel=\n" - "\" in\n" - "the body of a message to majordomo@vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + "Frankly I'd be happier of cp started to exploited fallocate() to create larger\n" + extents before copying data into them. Atleast for the large files. -0883322c7e59e718e9109c3f22939c5854c12559c3a59082f78defe466e4a5c7 +0f6d1a923178b2d0a1469b98e51269ceaccbf429b62da738052a11d125a701e6
diff --git a/a/1.txt b/N3/1.txt index d89f0f9..c81eea9 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -1,11 +1,9 @@ -On 06/29/2011 03:42 AM, P=E1draig Brady wrote: +On 06/29/2011 03:42 AM, Pádraig Brady wrote: > There is the argument, that if this interface can distinguish -> these dirty unwritten extents, then why can't the fiemap interface to= -o? +> these dirty unwritten extents, then why can't the fiemap interface too? > The advantage of the fiemap interface is that it can distinguish > empty extents vs holes. Empty extents will become increasingly common -> I think, given the fragmentation and space guarantee benefits they gi= -ve. +> I think, given the fragmentation and space guarantee benefits they give. > It would be cool for cp for example to be able to efficiently copy > empty extents from source to dest. @@ -13,11 +11,9 @@ I'm not too sure about that. Atleast not enabled by default. Most users use cp to backup data. Not empty space. In this case, this empty extent may not even be de-dupable. -=46rankly I'd be happier of cp started to exploited fallocate() to crea= -te larger +Frankly I'd be happier of cp started to exploited fallocate() to create larger extents before copying data into them. Atleast for the large files. -- -To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= -" in +To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N3/content_digest index b35a544..053dc17 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -17,14 +17,12 @@ " xfs@oss.sgi.com\0" "\00:1\0" "b\0" - "On 06/29/2011 03:42 AM, P=E1draig Brady wrote:\n" + "On 06/29/2011 03:42 AM, P\303\241draig Brady wrote:\n" "> There is the argument, that if this interface can distinguish\n" - "> these dirty unwritten extents, then why can't the fiemap interface to=\n" - "o?\n" + "> these dirty unwritten extents, then why can't the fiemap interface too?\n" "> The advantage of the fiemap interface is that it can distinguish\n" "> empty extents vs holes. Empty extents will become increasingly common\n" - "> I think, given the fragmentation and space guarantee benefits they gi=\n" - "ve.\n" + "> I think, given the fragmentation and space guarantee benefits they give.\n" "> It would be cool for cp for example to be able to efficiently copy\n" "> empty extents from source to dest.\n" "\n" @@ -32,13 +30,11 @@ "use cp to backup data. Not empty space. In this case, this empty extent\n" "may not even be de-dupable.\n" "\n" - "=46rankly I'd be happier of cp started to exploited fallocate() to crea=\n" - "te larger\n" + "Frankly I'd be happier of cp started to exploited fallocate() to create larger\n" "extents before copying data into them. Atleast for the large files.\n" "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-fsdevel=\n" - "\" in\n" + "To unsubscribe from this list: send the line \"unsubscribe linux-fsdevel\" in\n" "the body of a message to majordomo@vger.kernel.org\n" More majordomo info at http://vger.kernel.org/majordomo-info.html -0883322c7e59e718e9109c3f22939c5854c12559c3a59082f78defe466e4a5c7 +7cac90a99d2973e5cdb277ea60cf9b4c7919493b9bf2c09d61822d060ab8a2de
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.