public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: heiko.carstens@de.ibm.com, blaschka@linux.vnet.ibm.com,
	netdev@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH] net: cpu offline cause napi stall
Date: Tue, 07 Jun 2011 01:01:36 -0700 (PDT)	[thread overview]
Message-ID: <20110607.010136.1857896380762569754.davem@davemloft.net> (raw)
In-Reply-To: <1307429403.2642.77.camel@edumazet-laptop>

From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Tue, 07 Jun 2011 08:50:03 +0200

> From: Heiko Carstens <heiko.carstens@de.ibm.com>
> 
> Frank Blaschka reported :
> <quote>
>   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.
> </quote>
> 
> This patch is a straightforward implementation of Frank suggestion :
> 
> Transfert poll_list and trigger NET_RX_SOFTIRQ on new cpu.
> 
> Reported-by: Frank Blaschka <blaschka@linux.vnet.ibm.com>
> Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
> Tested-by: Eric Dumazet <eric.dumazet@gmail.com>

Applied, thanks everyone.

      parent reply	other threads:[~2011-06-07  8:01 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
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 [this message]

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=20110607.010136.1857896380762569754.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=blaschka@linux.vnet.ibm.com \
    --cc=eric.dumazet@gmail.com \
    --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