From: Oliver Hartkopp <socketcan@hartkopp•net>
To: "Butler, Peter" <pbutler@sonusnet•com>,
Rick Jones <rick.jones2@hpe•com>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>
Subject: Re: Poorer networking performance in later kernels?
Date: Tue, 19 Apr 2016 17:58:03 +0200 [thread overview]
Message-ID: <5716558B.2080103@hartkopp.net> (raw)
In-Reply-To: <SN1PR0301MB19983F545852731CD1410DB9D66C0@SN1PR0301MB1998.namprd03.prod.outlook.com>
On 04/19/2016 04:54 PM, Butler, Peter wrote:
>
> I think the issue is resolved. I had to recompile my 4.4.0 kernel with a few options pertaining to the Intel NIC which somehow (?) got left out or otherwise clobbered when I ported my 3.4.2 .config to the 4.4.0 kernel source tree. With those changes now in I see essentially identical performance with the two kernels. Sorry for any confusion and/or waste of time here. My bad.
>
Can you please send the relevant changes in the config that caused the
discussed issue?
Just in the case other people do a similar kernel upgrade from 3.x to a
recent kernel and the current defaults lead to this non-optimal result.
Thanks,
Oliver
next prev parent reply other threads:[~2016-04-19 15:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SN1PR0301MB19987565B71A4688593A2CDBD6680@SN1PR0301MB1998.namprd03.prod.outlook.com>
2016-04-15 21:02 ` Poorer networking performance in later kernels? Butler, Peter
2016-04-15 22:33 ` Eric Dumazet
2016-04-18 12:16 ` Eric Dumazet
2016-04-18 16:27 ` Butler, Peter
2016-04-18 18:05 ` Eric Dumazet
2016-04-18 16:44 ` Butler, Peter
2016-04-15 22:37 ` Rick Jones
2016-04-18 11:27 ` Butler, Peter
2016-04-18 18:22 ` Rick Jones
2016-04-19 14:54 ` Butler, Peter
2016-04-19 15:13 ` Josh Hunt
2016-04-19 15:47 ` Butler, Peter
2016-04-19 15:58 ` Oliver Hartkopp [this message]
2016-04-19 16:00 ` Butler, Peter
2016-04-19 16:13 ` David Miller
2016-04-18 12:02 ` Butler, Peter
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=5716558B.2080103@hartkopp.net \
--to=socketcan@hartkopp$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pbutler@sonusnet$(echo .)com \
--cc=rick.jones2@hpe$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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