netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Daniel Exner <dex@dragonslave.de>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Poor network performance x86_64.. also with 3.13
Date: Sun, 09 Feb 2014 10:14:34 -0800	[thread overview]
Message-ID: <1391969674.10160.134.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <20140209153107.GA8614@pd.tnic>

On Sun, 2014-02-09 at 16:31 +0100, Borislav Petkov wrote:
> On Sun, Feb 09, 2014 at 04:05:11PM +0100, Daniel Exner wrote:
> > > cat /etc/sysctl.d/net.conf
> > > net.ipv4.tcp_window_scaling = 1
> > > net.core.rmem_max = 16777216
> > > net.ipv4.tcp_rmem = 4096 87380 16777
> > > net.ipv4.tcp_wmem = 4096       1638
> > 
> > After removing those values I finally had sane iperf values.
> > No idea how those got there, perhaps they made sense when I first setup
> > the box, which is some years ago..
> 
> The only question that is left to clarify now is why do those values
> have effect on 3.12.x and not on 3.10...

tcp_rmem[2] = 16777

Come on, the 640KB barrier was broken a long time ago ;)

Feel free to investigate, I wont ;)

  reply	other threads:[~2014-02-09 18:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <52DAD66F.7080306@dragonslave.de>
2014-01-18 19:50 ` 3.12.8 poor network performance x86_64 Borislav Petkov
2014-01-18 22:46   ` Daniel Exner
2014-01-20 22:27     ` Poor network performance x86_64.. also with 3.13 Daniel Exner
2014-01-20 22:37       ` Borislav Petkov
2014-01-20 23:27         ` Branimir Maksimovic
2014-02-09 15:05         ` Daniel Exner
2014-02-09 15:31           ` Borislav Petkov
2014-02-09 18:14             ` Eric Dumazet [this message]
2014-02-09 18:49               ` Borislav Petkov

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=1391969674.10160.134.camel@edumazet-glaptop2.roam.corp.google.com \
    --to=eric.dumazet@gmail.com \
    --cc=bp@alien8.de \
    --cc=dex@dragonslave.de \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).