All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Haley <brian.haley@hp.com>
To: Wolfgang Walter <linux@stwm.de>, netdev@vger.kernel.org
Subject: Re: Big performance loss from 3.4.63 to 3.10.13 when routing ipv4
Date: Tue, 01 Oct 2013 14:57:33 -0400	[thread overview]
Message-ID: <524B1B1D.3050304@hp.com> (raw)
In-Reply-To: <3244031.uQGDddGTLF@h2o.as.studentenwerk.mhn.de>

On 10/01/2013 12:39 PM, Wolfgang Walter wrote:
> Hello,
> 
> I tried to upgrade one of our routers to 3.10.13 from 3.4.63 and I see a 
> dramatic performance loss. I tried 3.11.2 and it is still there.
> 
> *** Symptoms:
> 
> All network traffic over the router become slow and sluggish. If one pings the 
> router there is a packet loss. After about 2 minutes the traffic completely 
> stalls for about 1 minute. Then it works again as in the beginning to then 
> stall again. And so on.
> 
> This happens even with rather moderate traffic. While still routing the CPU 
> utilization is higher than it is with 3.4.63 but only moderately.
> 
> When it stalls no network traffic seems possible (but to loopback). If one 
> tries to ping from the router any target (even if it is on a interface with no 
> traffic at all) one gets:
> 
> 	ping: sendmsg: No buffer space available

dmesg show anything?  I've seen this happen when the neighbour table is full,
but that's not a typical occurence.

-Brian

  reply	other threads:[~2013-10-01 18:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-01 16:39 Big performance loss from 3.4.63 to 3.10.13 when routing ipv4 Wolfgang Walter
2013-10-01 18:57 ` Brian Haley [this message]
2013-10-01 19:44   ` Wolfgang Walter
2013-10-01 22:20 ` Hannes Frederic Sowa
2013-10-22 19:07   ` Wolfgang Walter
2013-10-22 19:46     ` David Miller
2013-10-23  8:12       ` Steffen Klassert
2013-10-23 11:33         ` Wolfgang Walter
2013-10-23 12:00           ` Eric Dumazet
2013-10-23 12:26             ` Steffen Klassert
2013-10-23 15:57             ` Wolfgang Walter
2013-10-23 12:04           ` Steffen Klassert
2013-10-23 16:05             ` Wolfgang Walter
     [not found] ` <3169911.kTmZ0BZVVr@h2o.as.studentenwerk.mhn.de>
     [not found]   ` <1382547992.7572.31.camel@edumazet-glaptop.roam.corp.google.com>
2013-10-23 22:52     ` Wolfgang Walter
2013-10-25  8:01       ` Steffen Klassert
2013-10-25  8:50         ` Eric Dumazet
2013-10-25  9:20           ` Steffen Klassert
2013-10-28  4:43             ` David Miller
2013-10-28  6:17             ` Eric Dumazet
2013-10-28 11:30               ` Steffen Klassert
2013-10-25  9:33         ` Wolfgang Walter
2013-10-24 11:07     ` Wolfgang Walter

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=524B1B1D.3050304@hp.com \
    --to=brian.haley@hp.com \
    --cc=linux@stwm.de \
    --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 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.