netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
To: netdev@vger.kernel.org
Cc: nikola.ciprich@linuxbox.cz
Subject: 4.4.0 - e1000e - possible power management issue
Date: Tue, 19 Apr 2016 21:53:44 +0200	[thread overview]
Message-ID: <20160419195344.GA8663@nik-comp.linuxbox.cz> (raw)

[-- Attachment #1: Type: text/plain, Size: 2565 bytes --]

Hi,

after upgrading our firewall from 4.1.17 to 4.4.0, we've noticed quite a performance
drop.. Slight network load seems to cause high CPU load..

running perf of almost idle system shows:

             samples  pcnt function                                DSO
             _______ _____ _______________________________________ ___________________________________________________________________________

              631.00 20.7% e1000_power_down_phy_copper_80003es2lan /lib/modules/4.4.0lb6.01/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
              191.00  6.3% do_raw_spin_lock                        [kernel.kallsyms]                                                          
              165.00  5.4% ipt_register_table                      /lib/modules/4.4.0lb6.01/kernel/net/ipv4/netfilter/ip_tables.ko            
              119.00  3.9% cache_init                              /usr/sbin/netstat-probe                                                    
              118.00  3.9% __memset_sse2                           /lib64/libc-2.12.so                                                        
               88.00  2.9% cache_write_packet                      /usr/sbin/netstat-probe                                                    
               41.00  1.3% __fget                                  [kernel.kallsyms]                                                          
               40.00  1.3% memcpy                                  [kernel.kallsyms]                                                          


when there is some network traffic, e1000_power_down_phy_copper_80003es2lan jumps to much higher
numbers.. as far as I understand the code, this seems suspicious to me..

Anyone hit the same problem?

I can try upgrading to 4.4.8-rc1 tomorrow or reverting to 4.1.17

lspci of the box adapters:

05:00.0 Ethernet controller: Intel Corporation 82573E Gigabit Ethernet Controller (Copper) (rev 03)
07:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller
09:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller
0b:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller

BR

nik

-- 
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 00 Ostrava

tel.:   +420 591 166 214
fax:    +420 596 621 273
mobil:  +420 777 093 799

www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

                 reply	other threads:[~2016-04-19 20:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160419195344.GA8663@nik-comp.linuxbox.cz \
    --to=nikola.ciprich@linuxbox.cz \
    --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).