All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <54E7E135.3060507@gmail.com>

diff --git a/a/1.txt b/N1/1.txt
index c4fcc78..4b09ca0 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -25,7 +25,7 @@ If I apply the solution there will appear the following problems
 My conclusion is write buffer in practice should be a single buffer and
 copying is inevitable.
 
-From a engineering point of view, memory copy can't be the bottleneck
+>From a engineering point of view, memory copy can't be the bottleneck
 (before that, SSD's throughput hits) so we shouldn't hack for the little
 improvement.
 
diff --git a/a/content_digest b/N1/content_digest
index 2817408..ae83840 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -11,10 +11,10 @@
  "Date\0Sat, 21 Feb 2015 10:36:53 +0900\0"
  "To\0ejt@redhat.com\0"
  "Cc\0Greg KH <gregkh@linuxfoundation.org>"
+  snitzer@redhat.com
   dm-devel@redhat.com
   driverdev-devel@linuxdriverproject.org
-  linux-kernel@vger.kernel.org
- " snitzer@redhat.com\0"
+ " linux-kernel@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
  "To be clear, bio's semantics doesn't require a io is written on\n"
@@ -44,7 +44,7 @@
  "My conclusion is write buffer in practice should be a single buffer and\n"
  "copying is inevitable.\n"
  "\n"
- "From a engineering point of view, memory copy can't be the bottleneck\n"
+ ">From a engineering point of view, memory copy can't be the bottleneck\n"
  "(before that, SSD's throughput hits) so we shouldn't hack for the little\n"
  "improvement.\n"
  "\n"
@@ -66,4 +66,4 @@
  ">\n"
  > - Joe
 
-80bbb619cc4e351fa3b579d95effea270b028b86dca2d005ca9037f701756ca0
+becd793a8155427f2675e7be0bac5c4b16b55937cd75752411184e9c8814ba26

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.