linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Damien Wyart <damien.wyart@free.fr>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Benjamin LaHaise <bcrl@lhnet.ca>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Denys Fedoryschenko <denys@visp.net.lb>,
	netdev@vger.kernel.org,
	linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: regression: unregister_netdev() unusably slow
Date: Mon, 25 May 2009 10:04:20 +0200	[thread overview]
Message-ID: <20090525080420.GA10127@localhost.localdomain> (raw)
In-Reply-To: <4A1A2AFA.8020605@cosmosbay.com>

Hello,

* Eric Dumazet <dada1@cosmosbay.com> [2009-05-25 07:22]:
> Time to include Paul and lkml in the discussion, and find a better
> solution than one provided in February.

> > bf51935f3e988e0ed6f34b55593e5912f990750a is first bad commit
> > commit bf51935f3e988e0ed6f34b55593e5912f990750a
> > Author: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> > Date:   Tue Feb 17 06:01:30 2009 -0800

> >     x86, rcu: fix strange load average and ksoftirqd behavior

> >     Damien Wyart reported high ksoftirqd CPU usage (20%) on an
> >     otherwise idle system.

> >     The function-graph trace Damien provided:
> > ...
> > diff --git a/arch/x86/kernel/process_32.c b/arch/x86/kernel/process_32.c

> > index a546f55..bd4da2a 100644
> > --- a/arch/x86/kernel/process_32.c
> > +++ b/arch/x86/kernel/process_32.c
> > @@ -104,9 +104,6 @@ void cpu_idle(void)
> >  			check_pgt_cache();
> >  			rmb();

> > -			if (rcu_pending(cpu))
> > -				rcu_check_callbacks(cpu, 0);
> > -
> >  			if (cpu_is_offline(cpu))
> >  				play_dead();

> I wonder if the real root of the problem was not discovered in the meantime,
> by commit 64ca5ab913f1594ef316556e65f5eae63ff50cee
> rcu: increment quiescent state counter in ksoftirqd()

> Maybe this commit solved Damien Wyart problem as well, and we can revert
> commit bf51935f3e988e0ed6f34b55593e5912f990750a ?

Ran some tests on 2.6.30-rc7 with bf51935f reverted, and I am still
seeing the problems I originally reported back in February, so I guess
64ca5ab9 is not enough to fully solve all the issues... Note that I am
using CONFIG_TREE_RCU=y (was already true in my February reports).

Feel free to ask if more testing is needed.

-- 
Damien Wyart

  reply	other threads:[~2009-05-25  8:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090524192150.GE24757@kvack.org>
     [not found] ` <200905250023.31056.denys@visp.net.lb>
     [not found]   ` <20090524213744.GG24757@kvack.org>
     [not found]     ` <4A19BF39.4000305@cosmosbay.com>
     [not found]       ` <20090524214433.GH24757@kvack.org>
     [not found]         ` <4A19C50B.9040304@cosmosbay.com>
     [not found]           ` <20090524221240.GI24757@kvack.org>
     [not found]             ` <4A19CE8B.3070302@cosmosbay.com>
     [not found]               ` <20090525000050.GJ24757@kvack.org>
2009-05-25  5:22                 ` regression: unregister_netdev() unusably slow Eric Dumazet
2009-05-25  8:04                   ` Damien Wyart [this message]
2009-05-25 16:21                   ` Paul E. McKenney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090525080420.GA10127@localhost.localdomain \
    --to=damien.wyart@free.fr \
    --cc=bcrl@lhnet.ca \
    --cc=dada1@cosmosbay.com \
    --cc=denys@visp.net.lb \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).