All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <CAA9_cmdx7T2jnfw6TvL0_3ytfs-h-X06uF3_7Ex-YP12YKpwng@mail.gmail.com>

diff --git a/a/1.txt b/N1/1.txt
index 29a47c0..3e09b80 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -17,8 +17,4 @@ go from here?
 I could go back to the FL_ALLOCATED approach, but use page idle callbacks
 instead of polling for the lease end notification. Or do we want to try
 busy extents? My concern with busy extents is that it requires more per-fs
-code.
-_______________________________________________
-Linux-nvdimm mailing list
-Linux-nvdimm@lists.01.org
-https://lists.01.org/mailman/listinfo/linux-nvdimm
\ No newline at end of file
+code.
\ No newline at end of file
diff --git a/N1/2.bin b/N1/2.bin
new file mode 100644
index 0000000..fc7a46a
--- /dev/null
+++ b/N1/2.bin
@@ -0,0 +1,7 @@
+<div><br></div>[replying from my phone, please forgive formatting]<br><br>On Friday, October 27, 2017, Dave Chinner &lt;<a href="mailto:david@fromorbit.com">david@fromorbit.com</a>&gt; wrote:<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+&gt; Here are the two primary patches in<br>
+&gt; the series, do you think the extent-busy approach would be cleaner?<br>
+<br>
+The XFS_DAXDMA....<br>
+<br>
+$DEITY that patch is so ugly I can&#39;t even bring myself to type it.</blockquote><div><br></div><div>Right, and so is the problem it&#39;s trying to solve. So where do you want to go from here?</div><div><br></div><div>I could go back to the FL_ALLOCATED approach, but use page idle callbacks instead of polling for the lease end notification. Or do we want to try busy extents? My concern with busy extents is that it requires more per-fs code.</div>
\ No newline at end of file
diff --git a/N1/2.hdr b/N1/2.hdr
new file mode 100644
index 0000000..a0dd15a
--- /dev/null
+++ b/N1/2.hdr
@@ -0,0 +1,2 @@
+Content-Type: text/html; charset="UTF-8"
+Content-Transfer-Encoding: quoted-printable
diff --git a/a/content_digest b/N1/content_digest
index 2f70230..f8a5cc3 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -39,27 +39,19 @@
   " paulus\@samba.org <paulus\@samba.org>",
   " Hefty",
   " Sean <sean.hefty\@intel.com>",
-  " hch\@lst.de <hch\@lst.de>",
+  " jlayton\@poochiereds.net <jlayton\@poochiereds.net>",
   " mawilcox\@microsoft.com <mawilcox\@microsoft.com>",
   " linux-rdma\@vger.kernel.org <linux-rdma\@vger.kernel.org>",
   " mpe\@ellerman.id.au <mpe\@ellerman.id.au>",
-  " jgunthorpe\@obsidianresearch.com <jgunthorpe\@obsidianresearch.com>",
   " dledford\@redhat.com <dledford\@redhat.com>",
+  " hch\@lst.de <hch\@lst.de>",
+  " jgunthorpe\@obsidianresearch.com <jgunthorpe\@obsidianresearch.com>",
   " hal.rosenstock\@gmail.com <hal.rosenstock\@gmail.com>",
-  " linux-nvdimm\@lists.01.org <linux-nvdimm\@lists.01.org>",
-  " viro\@zeniv.linux.org.uk <viro\@zeniv.linux.org.uk>",
-  " jlayton\@poochiereds.net <jlayton\@poochiereds.net>",
-  " gerald.schaefer\@de.ibm.com <gerald.schaefer\@de.ibm.com>",
-  " darrick.wong\@oracle.com <darrick.wong\@oracle.com>",
-  " linux-kernel\@vger.kernel.org <linux-kernel\@vger.kernel.org>",
-  " linux-xfs\@vger.kernel.org <linux-xfs\@vger.kernel.org>",
   " schwidefsky\@de.ibm.com <schwidefsky\@de.ibm.com>",
-  " linux-fsdevel\@vger.kernel.org <linux-fsdevel\@vger.kernel.org>",
-  " akpm\@linux-foundation.org <akpm\@linux-foundation.org>",
-  " kirill.shutemov\@linux.intel.com <kirill.shutemov\@linux.intel.com>\0"
+  " viro\@zeniv\0"
 ]
 [
-  "\0000:1\0"
+  "\0001:1\0"
 ]
 [
   "b\0"
@@ -84,11 +76,22 @@
   "I could go back to the FL_ALLOCATED approach, but use page idle callbacks\n",
   "instead of polling for the lease end notification. Or do we want to try\n",
   "busy extents? My concern with busy extents is that it requires more per-fs\n",
-  "code.\n",
-  "_______________________________________________\n",
-  "Linux-nvdimm mailing list\n",
-  "Linux-nvdimm\@lists.01.org\n",
-  "https://lists.01.org/mailman/listinfo/linux-nvdimm"
+  "code."
+]
+[
+  "\0001:2\0"
+]
+[
+  "b\0"
+]
+[
+  "<div><br></div>[replying from my phone, please forgive formatting]<br><br>On Friday, October 27, 2017, Dave Chinner &lt;<a href=\"mailto:david\@fromorbit.com\">david\@fromorbit.com</a>&gt; wrote:<div>\302\240</div><blockquote class=\"gmail_quote\" style=\"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex\">\r\n",
+  "&gt; Here are the two primary patches in<br>\r\n",
+  "&gt; the series, do you think the extent-busy approach would be cleaner?<br>\r\n",
+  "<br>\r\n",
+  "The XFS_DAXDMA....<br>\r\n",
+  "<br>\r\n",
+  "\$DEITY that patch is so ugly I can&#39;t even bring myself to type it.</blockquote><div><br></div><div>Right, and so is the problem it&#39;s trying to solve. So where do you want to go from here?</div><div><br></div><div>I could go back to the FL_ALLOCATED approach, but use page idle callbacks instead of polling for the lease end notification. Or do we want to try busy extents? My concern with busy extents is that it requires more per-fs code.</div>\r\n"
 ]
 
-55bf02cf344ae206c9f65d525058aa367512810b2dfb2dc17ddcfd3352645396
+65e036b4ef25ed1d09e4aac441ce72ceb6778f2a3aa93b47642b6fa076cc0636

diff --git a/a/1.txt b/N2/1.txt
index 29a47c0..3e09b80 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -17,8 +17,4 @@ go from here?
 I could go back to the FL_ALLOCATED approach, but use page idle callbacks
 instead of polling for the lease end notification. Or do we want to try
 busy extents? My concern with busy extents is that it requires more per-fs
-code.
-_______________________________________________
-Linux-nvdimm mailing list
-Linux-nvdimm@lists.01.org
-https://lists.01.org/mailman/listinfo/linux-nvdimm
\ No newline at end of file
+code.
\ No newline at end of file
diff --git a/N2/2.bin b/N2/2.bin
new file mode 100644
index 0000000..fc7a46a
--- /dev/null
+++ b/N2/2.bin
@@ -0,0 +1,7 @@
+<div><br></div>[replying from my phone, please forgive formatting]<br><br>On Friday, October 27, 2017, Dave Chinner &lt;<a href="mailto:david@fromorbit.com">david@fromorbit.com</a>&gt; wrote:<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+&gt; Here are the two primary patches in<br>
+&gt; the series, do you think the extent-busy approach would be cleaner?<br>
+<br>
+The XFS_DAXDMA....<br>
+<br>
+$DEITY that patch is so ugly I can&#39;t even bring myself to type it.</blockquote><div><br></div><div>Right, and so is the problem it&#39;s trying to solve. So where do you want to go from here?</div><div><br></div><div>I could go back to the FL_ALLOCATED approach, but use page idle callbacks instead of polling for the lease end notification. Or do we want to try busy extents? My concern with busy extents is that it requires more per-fs code.</div>
\ No newline at end of file
diff --git a/N2/2.hdr b/N2/2.hdr
new file mode 100644
index 0000000..a0dd15a
--- /dev/null
+++ b/N2/2.hdr
@@ -0,0 +1,2 @@
+Content-Type: text/html; charset="UTF-8"
+Content-Transfer-Encoding: quoted-printable
diff --git a/a/content_digest b/N2/content_digest
index 2f70230..12314a5 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -39,27 +39,27 @@
   " paulus\@samba.org <paulus\@samba.org>",
   " Hefty",
   " Sean <sean.hefty\@intel.com>",
-  " hch\@lst.de <hch\@lst.de>",
+  " jlayton\@poochiereds.net <jlayton\@poochiereds.net>",
   " mawilcox\@microsoft.com <mawilcox\@microsoft.com>",
   " linux-rdma\@vger.kernel.org <linux-rdma\@vger.kernel.org>",
   " mpe\@ellerman.id.au <mpe\@ellerman.id.au>",
-  " jgunthorpe\@obsidianresearch.com <jgunthorpe\@obsidianresearch.com>",
   " dledford\@redhat.com <dledford\@redhat.com>",
+  " hch\@lst.de <hch\@lst.de>",
+  " jgunthorpe\@obsidianresearch.com <jgunthorpe\@obsidianresearch.com>",
   " hal.rosenstock\@gmail.com <hal.rosenstock\@gmail.com>",
-  " linux-nvdimm\@lists.01.org <linux-nvdimm\@lists.01.org>",
+  " schwidefsky\@de.ibm.com <schwidefsky\@de.ibm.com>",
   " viro\@zeniv.linux.org.uk <viro\@zeniv.linux.org.uk>",
-  " jlayton\@poochiereds.net <jlayton\@poochiereds.net>",
   " gerald.schaefer\@de.ibm.com <gerald.schaefer\@de.ibm.com>",
+  " linux-nvdimm\@lists.01.org <linux-nvdimm\@lists.01.org>",
   " darrick.wong\@oracle.com <darrick.wong\@oracle.com>",
   " linux-kernel\@vger.kernel.org <linux-kernel\@vger.kernel.org>",
   " linux-xfs\@vger.kernel.org <linux-xfs\@vger.kernel.org>",
-  " schwidefsky\@de.ibm.com <schwidefsky\@de.ibm.com>",
   " linux-fsdevel\@vger.kernel.org <linux-fsdevel\@vger.kernel.org>",
   " akpm\@linux-foundation.org <akpm\@linux-foundation.org>",
   " kirill.shutemov\@linux.intel.com <kirill.shutemov\@linux.intel.com>\0"
 ]
 [
-  "\0000:1\0"
+  "\0001:1\0"
 ]
 [
   "b\0"
@@ -84,11 +84,22 @@
   "I could go back to the FL_ALLOCATED approach, but use page idle callbacks\n",
   "instead of polling for the lease end notification. Or do we want to try\n",
   "busy extents? My concern with busy extents is that it requires more per-fs\n",
-  "code.\n",
-  "_______________________________________________\n",
-  "Linux-nvdimm mailing list\n",
-  "Linux-nvdimm\@lists.01.org\n",
-  "https://lists.01.org/mailman/listinfo/linux-nvdimm"
+  "code."
+]
+[
+  "\0001:2\0"
+]
+[
+  "b\0"
+]
+[
+  "<div><br></div>[replying from my phone, please forgive formatting]<br><br>On Friday, October 27, 2017, Dave Chinner &lt;<a href=\"mailto:david\@fromorbit.com\">david\@fromorbit.com</a>&gt; wrote:<div>\302\240</div><blockquote class=\"gmail_quote\" style=\"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex\">\r\n",
+  "&gt; Here are the two primary patches in<br>\r\n",
+  "&gt; the series, do you think the extent-busy approach would be cleaner?<br>\r\n",
+  "<br>\r\n",
+  "The XFS_DAXDMA....<br>\r\n",
+  "<br>\r\n",
+  "\$DEITY that patch is so ugly I can&#39;t even bring myself to type it.</blockquote><div><br></div><div>Right, and so is the problem it&#39;s trying to solve. So where do you want to go from here?</div><div><br></div><div>I could go back to the FL_ALLOCATED approach, but use page idle callbacks instead of polling for the lease end notification. Or do we want to try busy extents? My concern with busy extents is that it requires more per-fs code.</div>\r\n"
 ]
 
-55bf02cf344ae206c9f65d525058aa367512810b2dfb2dc17ddcfd3352645396
+3f1e065280927abc2ad51cc6b6532ed422c0cbe2e4f0c43282d2d06403764ae7

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.