All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Eric Dumazet <eric.dumazet@gmail.com>
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, 9 Feb 2014 19:49:06 +0100	[thread overview]
Message-ID: <20140209184906.GC8487@pd.tnic> (raw)
In-Reply-To: <1391969674.10160.134.camel@edumazet-glaptop2.roam.corp.google.com>

On Sun, Feb 09, 2014 at 10:14:34AM -0800, Eric Dumazet wrote:
> tcp_rmem[2] = 16777
> 
> Come on, the 640KB barrier was broken a long time ago ;)
> 
> Feel free to investigate, I wont ;)

Me too - it's not like I don't have anything else to do. :-)

I was just wondering why 3.10 was fine even with these settings and 3.12
wasn't. Here's the original report:

"I recently upgraded the Kernel from version 3.10 to latest stable
3.12.8, did the usual "make oldconfig" (resulting config attached).

But now I noticed some _really_ low network performance."

Link: http://lkml.kernel.org/r/52DAD66F.7080306@dragonslave.de

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-18 19:30 3.12.8 poor network performance x86_64 Daniel Exner
2014-01-18 19:49 ` Holger Hoffstätte
2014-01-18 19:50 ` 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:05           ` Daniel Exner
2014-02-09 15:31           ` Borislav Petkov
2014-02-09 18:14             ` Eric Dumazet
2014-02-09 18:49               ` Borislav Petkov [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=20140209184906.GC8487@pd.tnic \
    --to=bp@alien8.de \
    --cc=dex@dragonslave.de \
    --cc=eric.dumazet@gmail.com \
    --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 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.