From: Rick Jones <rick.jones2@hp.com>
To: V JobNickname <workofv@gmail.com>, linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org
Subject: Re: network performance get regression from 2.6 to 3.10 by each version
Date: Mon, 05 May 2014 09:44:34 -0700 [thread overview]
Message-ID: <5367BFF2.50803@hp.com> (raw)
In-Reply-To: <CANHbGWu0SXtSSHDz=m6KCKOL7AESWB8GHbvqYJMUyvJpTZZDKA@mail.gmail.com>
On 05/02/2014 12:40 PM, V JobNickname wrote:
> I have an ARM platform which works with older 2.6.28 Linux Kernel and
> the embedded NIC driver
> I profile the TCP Tx using netperf 2.6 by command "./netperf -H
> {serverip} -l 300".
Is your ARM platform a multi-core one? If so, you may need/want to look
into making certain the assignment of NIC interrupts and netperf have
remained constant through your tests. You can bind netperf to a
specific CPU via either "taskset" or the global -T option. You can
check the interrupt assignment(s) for the queue(s) from the NIC by
looking at /proc/interrupts and perhaps via other means.
It would also be good to know if the drops in throughput correspond to
an increase in service demand (CPU per unit of work). To that end,
adding a global -c option to measure local (netperf side) CPU
utilization would be a good idea.
Still, even armed with that information, tracking down the regression or
regressions will be no small feat particularly since the timespan is so
long. A very good reason to be trying the newer versions as they
appear, even if only briefly, rather than leaving it for so long.
happy benchmarking,
rick jones
prev parent reply other threads:[~2014-05-05 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 19:40 network performance get regression from 2.6 to 3.10 by each version V JobNickname
2014-05-05 16:44 ` Rick Jones [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=5367BFF2.50803@hp.com \
--to=rick.jones2@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=workofv@gmail.com \
/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).