All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <200712071058.38416.arnd@arndb.de>

diff --git a/a/1.txt b/N1/1.txt
index 464f7db..8b43e7c 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,12 +1,10 @@
 On Thursday 06 December 2007, Roland Dreier wrote:
-> =A0> Regarding the performance problem, have you checked whether converti=
-ng all
-> =A0> your spin_lock_irqsave to spin_lock/spin_lock_irq improves your perf=
-ormance
-> =A0> on the older machines? Maybe it's already fast enough that way.
->=20
+>  > Regarding the performance problem, have you checked whether converting all
+>  > your spin_lock_irqsave to spin_lock/spin_lock_irq improves your performance
+>  > on the older machines? Maybe it's already fast enough that way.
+> 
 > It does seem that the only places that the hcall_lock is taken also
-> use msleep, so they must always be in process context. =A0So you can
+> use msleep, so they must always be in process context.  So you can
 > safely just use spin_lock(), right?
 
 I think it needs some more inspection. The msleep in there is only called
diff --git a/a/content_digest b/N1/content_digest
index cd5556f..2e8dd0e 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -16,14 +16,12 @@
  "\00:1\0"
  "b\0"
  "On Thursday 06 December 2007, Roland Dreier wrote:\n"
- "> =A0> Regarding the performance problem, have you checked whether converti=\n"
- "ng all\n"
- "> =A0> your spin_lock_irqsave to spin_lock/spin_lock_irq improves your perf=\n"
- "ormance\n"
- "> =A0> on the older machines? Maybe it's already fast enough that way.\n"
- ">=20\n"
+ "> \302\240> Regarding the performance problem, have you checked whether converting all\n"
+ "> \302\240> your spin_lock_irqsave to spin_lock/spin_lock_irq improves your performance\n"
+ "> \302\240> on the older machines? Maybe it's already fast enough that way.\n"
+ "> \n"
  "> It does seem that the only places that the hcall_lock is taken also\n"
- "> use msleep, so they must always be in process context. =A0So you can\n"
+ "> use msleep, so they must always be in process context. \302\240So you can\n"
  "> safely just use spin_lock(), right?\n"
  "\n"
  "I think it needs some more inspection. The msleep in there is only called\n"
@@ -33,4 +31,4 @@
  "\n"
  "\tArnd <><"
 
-70ebbcfa1ff027475daadc043fd384b783639668208fb9d0595d9aa2af38022f
+0d713e05f4c124ea84fa727f45322f4aa18802685257f28cf7011db3b0755c6a

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.