All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <87txtuyykr.fsf@codemonkey.ws>

diff --git a/a/1.txt b/N1/1.txt
index 491ff13..0675788 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -131,7 +131,7 @@ going to poll HPT based on how fast we can send data over the wire.
 > 16MiB is transferred in ~0.15 sec on GbE, much faster with 10GbE.  Does
 > it warrant a live migration protocol?
 
-0.15 sec = 150ms.  The typical downtime window is 30ms.  So yeah, I
+0.15 sec == 150ms.  The typical downtime window is 30ms.  So yeah, I
 think it does.
 
 >> Because it is a hash table, updates tend to be scattered throughout
diff --git a/a/content_digest b/N1/content_digest
index 59d0a7d..5325085 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -5,7 +5,7 @@
  "ref\0507D5BD9.3050700@redhat.com\0"
  "From\0Anthony Liguori <anthony@codemonkey.ws>\0"
  "Subject\0Re: [PATCH 5/5] KVM: PPC: Book3S HV: Provide a method for userspace to read and write the HPT\0"
- "Date\0Tue, 16 Oct 2012 20:03:00 +0000\0"
+ "Date\0Tue, 16 Oct 2012 15:03:00 -0500\0"
  "To\0Avi Kivity <avi@redhat.com>"
  " Paul Mackerras <paulus@samba.org>\0"
  "Cc\0Alexander Graf <agraf@suse.de>"
@@ -149,7 +149,7 @@
  "> 16MiB is transferred in ~0.15 sec on GbE, much faster with 10GbE.  Does\n"
  "> it warrant a live migration protocol?\n"
  "\n"
- "0.15 sec = 150ms.  The typical downtime window is 30ms.  So yeah, I\n"
+ "0.15 sec == 150ms.  The typical downtime window is 30ms.  So yeah, I\n"
  "think it does.\n"
  "\n"
  ">> Because it is a hash table, updates tend to be scattered throughout\n"
@@ -196,4 +196,4 @@
  "> -- \n"
  > error compiling committee.c: too many arguments to function
 
-cc6f138899383a2b730ed0f4e7caa4cdf626819d5e0c722e04b6ec4013e4690e
+618e8de2148dd05af878f6895e0d0e16f348d4b6c82cb6064cfcbc2816ccce49

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.