netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: zhou rui <zhourui.cn@gmail.com>
To: netdev@vger.kernel.org
Cc: jon.zhou@jdsu.com
Subject: same application has different performance with kernel 2.6.32/34/36
Date: Fri, 29 Apr 2011 22:46:04 +0800	[thread overview]
Message-ID: <BANLkTinF8Mfs+pqfGV0bLqm_3VyKCMn0LA@mail.gmail.com> (raw)

hi
my test application add a packet hook via  dev_add_pack(&prot_hook);
then copy the packet to a shared memory between userspace and kernel

tests wereperformed at same machine(DL380 G7, 12cores, intel X520 10G
nic),same traffic,same nic driver(ixgbe 3.3.9)

kernel 2.6.32.12 (SUSE SLES11,SP1)
APPlication cpu usage: 5-6%


kernel updated to  2.6.34.7
APPlication cpu usage: 19-25%

kernel 2.6.36.4 (enable/disable RPS)
APPlication cpu usage 35-40%


before I installing profile tool to find the root cause, any idea about it?
'top' result is not accurate  in older kernel? or any kernel
module/feature impact this?

             reply	other threads:[~2011-04-29 14:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 14:46 zhou rui [this message]
2011-04-29 15:48 ` same application has different performance with kernel 2.6.32/34/36 Stephen Hemminger

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=BANLkTinF8Mfs+pqfGV0bLqm_3VyKCMn0LA@mail.gmail.com \
    --to=zhourui.cn@gmail.com \
    --cc=jon.zhou@jdsu.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 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).