All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20110427220220.GP2135@linux.vnet.ibm.com>

diff --git a/a/1.txt b/N1/1.txt
index 3e07048..4fddfb0 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -137,3 +137,10 @@ So they look fine to me, the ones that I understand, anyway.  ;-)
 > > the body of a message to majordomo@vger.kernel.org
 > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
 > >
+
+--
+To unsubscribe, send a message with 'unsubscribe linux-mm' in
+the body to majordomo@kvack.org.  For more info on Linux MM,
+see: http://www.linux-mm.org/ .
+Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
+Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
diff --git a/a/content_digest b/N1/content_digest
index 9cce3b0..b65f756 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -163,6 +163,13 @@
  "> > 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 \302\240http://vger.kernel.org/majordomo-info.html\n"
- > >
+ "> >\n"
+ "\n"
+ "--\n"
+ "To unsubscribe, send a message with 'unsubscribe linux-mm' in\n"
+ "the body to majordomo@kvack.org.  For more info on Linux MM,\n"
+ "see: http://www.linux-mm.org/ .\n"
+ "Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/\n"
+ "Don't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>"
 
-55d77cbee068c26a318a2337eb4202938699e1a839c0c2f12505d1d613130fbf
+81bfbf07160eacfc1945b7cef7b574cf332b7c12b0c725f9b6e38c911d6c4ec1

diff --git a/a/1.txt b/N2/1.txt
index 3e07048..02664bc 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -2,22 +2,22 @@ On Tue, Apr 26, 2011 at 09:17:28PM +0200, Sedat Dilek wrote:
 > On Tue, Apr 26, 2011 at 8:50 PM, Paul E. McKenney
 > <paulmck@linux.vnet.ibm.com> wrote:
 > > On Tue, Apr 26, 2011 at 10:12:39AM -0700, Linus Torvalds wrote:
-> >> On Tue, Apr 26, 2011 at 9:38 AM, Bruno Prémont
+> >> On Tue, Apr 26, 2011 at 9:38 AM, Bruno Premont
 > >> <bonbons@linux-vserver.org> wrote:
 > >> >
 > >> > Here it comes:
 > >> >
 > >> > rcu_kthread (when build processes are STOPped):
-> >> > [  836.050003] rcu_kthread     R running   7324     6      2 0x00000000
-> >> > [  836.050003]  dd473f28 00000046 5a000240 dd65207c dd407360 dd651d40 0000035c dd473ed8
-> >> > [  836.050003]  c10bf8a2 c14d63d8 dd65207c dd473f28 dd445040 dd445040 dd473eec c10be848
-> >> > [  836.050003]  dd651d40 dd407360 ddfdca00 dd473f14 c10bfde2 00000000 00000001 000007b6
-> >> > [  836.050003] Call Trace:
-> >> > [  836.050003]  [<c10bf8a2>] ? check_object+0x92/0x210
-> >> > [  836.050003]  [<c10be848>] ? init_object+0x38/0x70
-> >> > [  836.050003]  [<c10bfde2>] ? free_debug_processing+0x112/0x1f0
-> >> > [  836.050003]  [<c103d9fd>] ? lock_timer_base+0x2d/0x70
-> >> > [  836.050003]  [<c13c8ec7>] schedule_timeout+0x137/0x280
+> >> > [  836.050003] rcu_kthread     R running   7324     6      2 0x00000000
+> >> > [  836.050003]  dd473f28 00000046 5a000240 dd65207c dd407360 dd651d40 0000035c dd473ed8
+> >> > [  836.050003]  c10bf8a2 c14d63d8 dd65207c dd473f28 dd445040 dd445040 dd473eec c10be848
+> >> > [  836.050003]  dd651d40 dd407360 ddfdca00 dd473f14 c10bfde2 00000000 00000001 000007b6
+> >> > [  836.050003] Call Trace:
+> >> > [  836.050003]  [<c10bf8a2>] ? check_object+0x92/0x210
+> >> > [  836.050003]  [<c10be848>] ? init_object+0x38/0x70
+> >> > [  836.050003]  [<c10bfde2>] ? free_debug_processing+0x112/0x1f0
+> >> > [  836.050003]  [<c103d9fd>] ? lock_timer_base+0x2d/0x70
+> >> > [  836.050003]  [<c13c8ec7>] schedule_timeout+0x137/0x280
 > >>
 > >> Hmm.
 > >>
@@ -36,24 +36,24 @@ On Tue, Apr 26, 2011 at 09:17:28PM +0200, Sedat Dilek wrote:
 > >> regular tree-RCU.
 > >
 > > The difference between TINY_RCU and TREE_RCU is that TREE_RCU still uses
-> > softirq for the core RCU processing.  TINY_RCU switched to a kthread
-> > when I implemented RCU priority boosting.  There is a similar change in
+> > softirq for the core RCU processing.  TINY_RCU switched to a kthread
+> > when I implemented RCU priority boosting.  There is a similar change in
 > > my -rcu tree that makes TREE_RCU use kthreads, and Sedat has been running
-> > into a very similar problem with that change in place.  Which is why I
+> > into a very similar problem with that change in place.  Which is why I
 > > do not yet push it to the -next tree.
 > >
 > >> This is without CONFIG_RCU_BOOST_PRIO, so we basically have
 > >>
-> >>         struct sched_param sp;
+> >>         struct sched_param sp;
 > >>
-> >>         rcu_kthread_task = kthread_run(rcu_kthread, NULL, "rcu_kthread");
-> >>         sp.sched_priority = RCU_BOOST_PRIO;
-> >>         sched_setscheduler_nocheck(rcu_kthread_task, SCHED_FIFO, &sp);
+> >>         rcu_kthread_task = kthread_run(rcu_kthread, NULL, "rcu_kthread");
+> >>         sp.sched_priority = RCU_BOOST_PRIO;
+> >>         sched_setscheduler_nocheck(rcu_kthread_task, SCHED_FIFO, &sp);
 > >>
 > >> where RCU_BOOST_PRIO is 1 for the non-boost case.
 > >
-> > Good point!  Bruno, Sedat, could you please set CONFIG_RCU_BOOST_PRIO to
-> > (say) 50, and see if this still happens?  (I bet that you do, but...)
+> > Good point!  Bruno, Sedat, could you please set CONFIG_RCU_BOOST_PRIO to
+> > (say) 50, and see if this still happens?  (I bet that you do, but...)
 > >
 > 
 > What's with CONFIG_RCU_BOOST_DELAY setting?
@@ -124,16 +124,23 @@ So they look fine to me, the ones that I understand, anyway.  ;-)
 > >> Any ideas?
 > >
 > > I have found one bug so far in my code, but it only affects TREE_RCU
-> > in my -rcu tree, and even then only if HOTPLUG_CPU is enabled.  I am
+> > in my -rcu tree, and even then only if HOTPLUG_CPU is enabled.  I am
 > > testing a fix, but I expect Sedat's tests to still break.
 > >
 > > I gave Sedat a patch that make rcu_kthread() run at normal (non-realtime)
-> > priority, and he did not see the failure.  So running non-realtime at
+> > priority, and he did not see the failure.  So running non-realtime at
 > > least greatly reduces the probability of failure.
 > >
-> >                                                        Thanx, Paul
+> >                                                        Thanx, Paul
 > > --
 > > 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
+> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
 > >
+
+--
+To unsubscribe, send a message with 'unsubscribe linux-mm' in
+the body to majordomo@kvack.org.  For more info on Linux MM,
+see: http://www.linux-mm.org/ .
+Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
+Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
diff --git a/a/content_digest b/N2/content_digest
index 9cce3b0..8ecadad 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -29,22 +29,22 @@
  "> On Tue, Apr 26, 2011 at 8:50 PM, Paul E. McKenney\n"
  "> <paulmck@linux.vnet.ibm.com> wrote:\n"
  "> > On Tue, Apr 26, 2011 at 10:12:39AM -0700, Linus Torvalds wrote:\n"
- "> >> On Tue, Apr 26, 2011 at 9:38 AM, Bruno Pr\303\251mont\n"
+ "> >> On Tue, Apr 26, 2011 at 9:38 AM, Bruno Premont\n"
  "> >> <bonbons@linux-vserver.org> wrote:\n"
  "> >> >\n"
  "> >> > Here it comes:\n"
  "> >> >\n"
  "> >> > rcu_kthread (when build processes are STOPped):\n"
- "> >> > [ \302\240836.050003] rcu_kthread \302\240 \302\240 R running \302\240 7324 \302\240 \302\240 6 \302\240 \302\240 \302\2402 0x00000000\n"
- "> >> > [ \302\240836.050003] \302\240dd473f28 00000046 5a000240 dd65207c dd407360 dd651d40 0000035c dd473ed8\n"
- "> >> > [ \302\240836.050003] \302\240c10bf8a2 c14d63d8 dd65207c dd473f28 dd445040 dd445040 dd473eec c10be848\n"
- "> >> > [ \302\240836.050003] \302\240dd651d40 dd407360 ddfdca00 dd473f14 c10bfde2 00000000 00000001 000007b6\n"
- "> >> > [ \302\240836.050003] Call Trace:\n"
- "> >> > [ \302\240836.050003] \302\240[<c10bf8a2>] ? check_object+0x92/0x210\n"
- "> >> > [ \302\240836.050003] \302\240[<c10be848>] ? init_object+0x38/0x70\n"
- "> >> > [ \302\240836.050003] \302\240[<c10bfde2>] ? free_debug_processing+0x112/0x1f0\n"
- "> >> > [ \302\240836.050003] \302\240[<c103d9fd>] ? lock_timer_base+0x2d/0x70\n"
- "> >> > [ \302\240836.050003] \302\240[<c13c8ec7>] schedule_timeout+0x137/0x280\n"
+ "> >> > [  836.050003] rcu_kthread     R running   7324     6      2 0x00000000\n"
+ "> >> > [  836.050003]  dd473f28 00000046 5a000240 dd65207c dd407360 dd651d40 0000035c dd473ed8\n"
+ "> >> > [  836.050003]  c10bf8a2 c14d63d8 dd65207c dd473f28 dd445040 dd445040 dd473eec c10be848\n"
+ "> >> > [  836.050003]  dd651d40 dd407360 ddfdca00 dd473f14 c10bfde2 00000000 00000001 000007b6\n"
+ "> >> > [  836.050003] Call Trace:\n"
+ "> >> > [  836.050003]  [<c10bf8a2>] ? check_object+0x92/0x210\n"
+ "> >> > [  836.050003]  [<c10be848>] ? init_object+0x38/0x70\n"
+ "> >> > [  836.050003]  [<c10bfde2>] ? free_debug_processing+0x112/0x1f0\n"
+ "> >> > [  836.050003]  [<c103d9fd>] ? lock_timer_base+0x2d/0x70\n"
+ "> >> > [  836.050003]  [<c13c8ec7>] schedule_timeout+0x137/0x280\n"
  "> >>\n"
  "> >> Hmm.\n"
  "> >>\n"
@@ -63,24 +63,24 @@
  "> >> regular tree-RCU.\n"
  "> >\n"
  "> > The difference between TINY_RCU and TREE_RCU is that TREE_RCU still uses\n"
- "> > softirq for the core RCU processing. \302\240TINY_RCU switched to a kthread\n"
- "> > when I implemented RCU priority boosting. \302\240There is a similar change in\n"
+ "> > softirq for the core RCU processing.  TINY_RCU switched to a kthread\n"
+ "> > when I implemented RCU priority boosting.  There is a similar change in\n"
  "> > my -rcu tree that makes TREE_RCU use kthreads, and Sedat has been running\n"
- "> > into a very similar problem with that change in place. \302\240Which is why I\n"
+ "> > into a very similar problem with that change in place.  Which is why I\n"
  "> > do not yet push it to the -next tree.\n"
  "> >\n"
  "> >> This is without CONFIG_RCU_BOOST_PRIO, so we basically have\n"
  "> >>\n"
- "> >> \302\240 \302\240 \302\240 \302\240 struct sched_param sp;\n"
+ "> >>         struct sched_param sp;\n"
  "> >>\n"
- "> >> \302\240 \302\240 \302\240 \302\240 rcu_kthread_task = kthread_run(rcu_kthread, NULL, \"rcu_kthread\");\n"
- "> >> \302\240 \302\240 \302\240 \302\240 sp.sched_priority = RCU_BOOST_PRIO;\n"
- "> >> \302\240 \302\240 \302\240 \302\240 sched_setscheduler_nocheck(rcu_kthread_task, SCHED_FIFO, &sp);\n"
+ "> >>         rcu_kthread_task = kthread_run(rcu_kthread, NULL, \"rcu_kthread\");\n"
+ "> >>         sp.sched_priority = RCU_BOOST_PRIO;\n"
+ "> >>         sched_setscheduler_nocheck(rcu_kthread_task, SCHED_FIFO, &sp);\n"
  "> >>\n"
  "> >> where RCU_BOOST_PRIO is 1 for the non-boost case.\n"
  "> >\n"
- "> > Good point! \302\240Bruno, Sedat, could you please set CONFIG_RCU_BOOST_PRIO to\n"
- "> > (say) 50, and see if this still happens? \302\240(I bet that you do, but...)\n"
+ "> > Good point!  Bruno, Sedat, could you please set CONFIG_RCU_BOOST_PRIO to\n"
+ "> > (say) 50, and see if this still happens?  (I bet that you do, but...)\n"
  "> >\n"
  "> \n"
  "> What's with CONFIG_RCU_BOOST_DELAY setting?\n"
@@ -151,18 +151,25 @@
  "> >> Any ideas?\n"
  "> >\n"
  "> > I have found one bug so far in my code, but it only affects TREE_RCU\n"
- "> > in my -rcu tree, and even then only if HOTPLUG_CPU is enabled. \302\240I am\n"
+ "> > in my -rcu tree, and even then only if HOTPLUG_CPU is enabled.  I am\n"
  "> > testing a fix, but I expect Sedat's tests to still break.\n"
  "> >\n"
  "> > I gave Sedat a patch that make rcu_kthread() run at normal (non-realtime)\n"
- "> > priority, and he did not see the failure. \302\240So running non-realtime at\n"
+ "> > priority, and he did not see the failure.  So running non-realtime at\n"
  "> > least greatly reduces the probability of failure.\n"
  "> >\n"
- "> > \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240Thanx, Paul\n"
+ "> >                                                        Thanx, Paul\n"
  "> > --\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 \302\240http://vger.kernel.org/majordomo-info.html\n"
- > >
+ "> > More majordomo info at  http://vger.kernel.org/majordomo-info.html\n"
+ "> >\n"
+ "\n"
+ "--\n"
+ "To unsubscribe, send a message with 'unsubscribe linux-mm' in\n"
+ "the body to majordomo@kvack.org.  For more info on Linux MM,\n"
+ "see: http://www.linux-mm.org/ .\n"
+ "Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/\n"
+ "Don't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>"
 
-55d77cbee068c26a318a2337eb4202938699e1a839c0c2f12505d1d613130fbf
+815de6d9ae4e9f71b2dc9e1085bfb585deb39ac66993c7300ed04fd5f938afa5

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.