All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: netdev <netdev@vger.kernel.org>
Subject: Performance regression between 4.13 and 4.14
Date: Tue, 8 May 2018 09:44:06 -0700	[thread overview]
Message-ID: <9115910b-dd8b-e7f3-be53-f739b8382032@candelatech.com> (raw)

Hello,

I am trying to track down a performance regression that appears to be between 4.13
and 4.14.

I first saw the problem with a hacked version of pktgen on some ixgbe NICs.  4.13 can do
right at 10G bi-directional on two ports, and 4.14 and later can do only about 6Gbps.

I also tried with user-space UDP traffic on a stock kernel, and I can get about 3.2Gbps combined tx+rx
on 4.14 and about 4.4Gbps on 4.13.

Attempting to bisect seems to be triggering a weirdness in git, and also lots of commits
crash or do not bring up networking, which makes the bisect difficult.

Looking at perf top, it would appear that some lock is probably to blame.

Any ideas what might have been introduced during this interval that
would cause this?

Anyone else seen similar?

I'm going to attempt some more manual steps to try to find the commit that
introduces this...

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

             reply	other threads:[~2018-05-08 16:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08 16:44 Ben Greear [this message]
2018-05-08 17:10 ` Performance regression between 4.13 and 4.14 Eric Dumazet
2018-05-09 18:43   ` Ben Greear
2018-05-09 18:48     ` Eric Dumazet
2018-05-09 19:02       ` Ben Greear
2018-05-09 20:55         ` Ben Greear

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=9115910b-dd8b-e7f3-be53-f739b8382032@candelatech.com \
    --to=greearb@candelatech.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 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.