public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Frank Blaschka <blaschka@linux.vnet.ibm.com>,
	davem@davemloft.net, netdev@vger.kernel.org,
	linux-s390@vger.kernel.org
Subject: Re: [BUG] net: cpu offline cause napi stall
Date: Wed, 01 Jun 2011 18:55:21 +0200	[thread overview]
Message-ID: <1306947321.2890.5.camel@edumazet-laptop> (raw)
In-Reply-To: <20110601163628.GA2418@osiris.boeblingen.de.ibm.com>

Le mercredi 01 juin 2011 à 18:36 +0200, Heiko Carstens a écrit :
> On Wed, Jun 01, 2011 at 02:13:19PM +0200, Eric Dumazet wrote:
> > Le mercredi 01 juin 2011 à 12:33 +0200, Frank Blaschka a écrit :
> > > Hi Dave, Eric,
> > > 
> > > during heavy network load we turn off/on cpus.
> > > Sometimes this causes a stall on the network device.
> > > Digging into the dump I found out following:
> > > 
> > > napi is scheduled but does not run. From the I/O buffers
> > > and the napi state I see napi/rx_softirq processing has stopped
> > > because the budget was reached. napi stays in the
> > > softnet_data poll_list and the rx_softirq was raised again.
> > > 
> > > I assume at this time the cpu offline comes in.
> > > the rx softirq is raised/moved to another cpu but napi stays in the poll_list
> > > of the softnet_data of the now offline cpu.
> > > 
> > > reviewing dev_cpu_callback (net/core/dev.c) I did not find the poll_list
> > > is transfered to the new cpu. Do you think this could cause the stall or
> > > did I miss something?
> > > 
> > > Thx for your help.
> > 
> > Hi Frank
> > 
> > I believe you are right, I cant see where the poll_list transfert from
> > dead cpu to online cpu is done.
> > 
> > Do you want to prepare a patch ?
> 
> Frank will be offline until next week. I assume the patch below would fix
> the problem, however its untested. I doubt we can verify that it really
> fixes the problem also until next week (public holiday tomorrow).
> 
> diff --git a/net/core/dev.c b/net/core/dev.c
> index 6561021..6d6a7cf 100644
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -5981,6 +5981,8 @@ static int dev_cpu_callback(struct notifier_block *nfb,
>  		oldsd->output_queue = NULL;
>  		oldsd->output_queue_tailp = &oldsd->output_queue;
>  	}
> +	/* Append NAPI poll list from offline CPU. */
> +	list_splice_init(&oldsd->poll_list, &sd->poll_list);
>  
>  	raise_softirq_irqoff(NET_TX_SOFTIRQ);
>  	local_irq_enable();

Same here, I'll be offline for the next 4 days ;)

Please make sure we raise NET_RX_SOFTIRQ on new cpu if necessary.

  reply	other threads:[~2011-06-01 16:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01 10:33 [BUG] net: cpu offline cause napi stall Frank Blaschka
2011-06-01 12:13 ` Eric Dumazet
2011-06-01 16:36   ` Heiko Carstens
2011-06-01 16:55     ` Eric Dumazet [this message]
2011-06-01 18:12       ` Heiko Carstens
2011-06-01 20:03         ` Eric Dumazet
2011-06-01 20:42           ` Heiko Carstens
2011-06-06 21:50             ` David Miller
2011-06-07  6:50               ` [PATCH] " Eric Dumazet
2011-06-07  7:09                 ` Eric Dumazet
2011-06-07  8:01                 ` David Miller

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=1306947321.2890.5.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=blaschka@linux.vnet.ibm.com \
    --cc=davem@davemloft.net \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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