Netdev List
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>,
	Akshat Kakkar <akshat.1984@gmail.com>
Cc: David Laight <David.Laight@aculab.com>, netdev <netdev@vger.kernel.org>
Subject: Re: Something hitting my total number of connections to the server
Date: Tue, 22 Aug 2017 09:43:45 -0700	[thread overview]
Message-ID: <bf580154-aea9-4143-5d9c-df3764b5e745@gmail.com> (raw)
In-Reply-To: <1503406926.2499.20.camel@edumazet-glaptop3.roam.corp.google.com>

On 8/22/17 6:02 AM, Eric Dumazet wrote:
>>
>> net.core.netdev_max_backlog=10000
> This is an insane backlog.
> 

https://www.kernel.org/doc/Documentation/networking/scaling.txt

"== Suggested Configuration

Flow limit is useful on systems with many concurrent connections,
where a single connection taking up 50% of a CPU indicates a problem.
In such environments, enable the feature on all CPUs that handle
network rx interrupts (as set in /proc/irq/N/smp_affinity).

The feature depends on the input packet queue length to exceed
the flow limit threshold (50%) + the flow history length (256).
Setting net.core.netdev_max_backlog to either 1000 or 10000
performed well in experiments."

  reply	other threads:[~2017-08-22 16:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14  9:07 Something hitting my total number of connections to the server Akshat Kakkar
2017-08-16  4:48 ` Akshat Kakkar
2017-08-16 10:34   ` Eric Dumazet
2017-08-17  9:05     ` Akshat Kakkar
2017-08-17 11:36       ` Eric Dumazet
2017-08-18  9:14         ` Akshat Kakkar
2017-08-18 12:06           ` Eric Dumazet
2017-08-18 12:44             ` Akshat Kakkar
2017-08-18 12:57               ` Eric Dumazet
2017-08-21  9:43           ` David Laight
2017-08-21  9:56             ` Akshat Kakkar
2017-08-21 14:17               ` Neal Cardwell
2017-08-21 15:17               ` Eric Dumazet
2017-08-21 17:28                 ` Akshat Kakkar
2017-08-21 17:44                   ` Eric Dumazet
2017-08-21 17:44                     ` Eric Dumazet
2017-08-22  5:42                       ` Akshat Kakkar
2017-08-22  5:44                         ` Akshat Kakkar
2017-08-22 12:28                         ` Neal Cardwell
2017-08-23  5:08                           ` Akshat Kakkar
2017-08-23 13:35                             ` Neal Cardwell
2017-08-22 13:02                         ` Eric Dumazet
2017-08-22 16:43                           ` David Ahern [this message]
2017-08-22 17:44                             ` Eric Dumazet
2017-08-22 17:46                               ` David Ahern
2017-08-22 17:50                                 ` Eric Dumazet

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=bf580154-aea9-4143-5d9c-df3764b5e745@gmail.com \
    --to=dsahern@gmail.com \
    --cc=David.Laight@aculab.com \
    --cc=akshat.1984@gmail.com \
    --cc=eric.dumazet@gmail.com \
    --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