From: jamal <hadi@cyberus.ca>
To: David Miller <davem@davemloft.net>
Cc: Robert.Olsson@data.slu.se, johnpol@2ka.mipt.ru,
krkumar2@in.ibm.com, gaagaan@gmail.com, netdev@vger.kernel.org,
rick.jones2@hp.com, sri@us.ibm.com
Subject: FSCKED clock sources WAS(Re: [WIP][PATCHES] Network xmit batching
Date: Thu, 21 Jun 2007 11:54:17 -0400 [thread overview]
Message-ID: <1182441257.5017.48.camel@localhost> (raw)
In-Reply-To: <20070619.152801.99185860.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
On Tue, 2007-19-06 at 15:28 -0700, David Miller wrote:
> Converting pktgen over to ktime_t might be a nice cleanup.
Would that really solve it? i.e doesnt it still tie to what the clock
source is?
I had a friend of mine (Robert, you know Jeremy) and results are
slightly different from what Evginy found.
The summary is: Batching always is better, jiffies is always the better
clock source (and who would have thunk,eh? Opteron kicks a Xeons ass).
Attached results.
Evgeniy, did you sync on the batching case with the git tree?
Can you describe your hardware in /proc/cpuinfo and /proc/interupts?
cheers,
jamal
[-- Attachment #2: batch-clock-res --]
[-- Type: text/plain, Size: 2630 bytes --]
The test variables are:
----------------------
1) A Intel Xeon[1] machine vs an AMD opteron[2].
2) A plain 2622-rc4 kernel vs a 2622-rc4 with batching
(from git://git.kernel.org/pub/scm/linux/kernel/git/hadi/batch-lin26.git)
3) Different clock sources acpi-pm, jiffies and tsc
Test setup
-----------
pktgen was used to send from the system under test (where
test variables #2-#3 were adjusted) to a second box.
CPU affinity was tied to cpu2 in all case to reduce variables in all test
cases...
Test validation
---------------
Throughput results were confirmed to match on receiver
and sender (as reported by pktgen)
Results
-------
The AMD opteron always had better results.
The batching kernels always was better than non-batching.
The jiffies clock was always the most consistent and gave
best performance
Kernel-type | acpi-pm clock | jiffies clock | tsc clock |
+h/ware | | | |
------------+---------------+---------------+-----------+
2622-rc4 | 347Kpps | 1.40 Mpps | 1.36Mpps |
plain | | | |
Intel Xeon | | | |
------------+---------------+---------------+-----------+
2622-rc4 | 342Kpps | 853 kpps | 821kpps |
plain | | | |
AMD opteron | | | |
------------+---------------+---------------+-----------+
2622-rc4 | 615Kpps | 1.46 Mpps | 1.46Mpps |
batch | | | |
Intel Xeon | | | |
------------+---------------+---------------+-----------+
2622-rc4 | 633Kpps | 1.18 Mpps | 1.17Mpps |
batch | | | |
AMD opteron | | | |
------------+---------------+---------------+-----------+
The two systems under test
---------------------------
[1]-------------
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel(R) Xeon(TM) CPU 2.80GHz
stepping : 1
cpu MHz : 2793.329
cache size : 1024 KB
physical id : 3
siblings : 2
core id : 0
cpu cores : 1
-------------
[2]-------------
vendor_id : AuthenticAMD
cpu family : 15
model : 33
model name : Dual Core AMD Opteron(tm) Processor 275
stepping : 2
cpu MHz : 2194.778
cache size : 1024 KB
physical id : 1
siblings : 2
core id : 1
cpu cores : 2
---------------------------------------------
next prev parent reply other threads:[~2007-06-21 15:54 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 13:49 [WIP][PATCHES] Network xmit batching jamal
2007-06-07 6:16 ` Krishna Kumar2
2007-06-07 11:43 ` jamal
2007-06-07 16:13 ` Evgeniy Polyakov
2007-06-07 22:23 ` jamal
2007-06-08 8:38 ` Evgeniy Polyakov
2007-06-08 11:31 ` jamal
2007-06-08 12:09 ` Evgeniy Polyakov
2007-06-08 13:07 ` jamal
2007-06-08 21:02 ` Evgeniy Polyakov
2007-06-08 5:05 ` Krishna Kumar2
2007-06-19 13:21 ` Evgeniy Polyakov
2007-06-19 13:33 ` Evgeniy Polyakov
2007-06-19 14:00 ` Evgeniy Polyakov
2007-06-19 14:09 ` Evgeniy Polyakov
2007-06-19 16:32 ` jamal
2007-06-19 16:44 ` Evgeniy Polyakov
2007-06-19 16:28 ` jamal
2007-06-19 16:35 ` Evgeniy Polyakov
2007-06-19 16:45 ` Evgeniy Polyakov
2007-06-19 17:35 ` Robert Olsson
2007-06-19 17:48 ` jamal
2007-06-19 17:55 ` Evgeniy Polyakov
2007-06-28 0:05 ` [WIP][PATCHES] Network xmit batching - tg3 support jamal
2007-07-02 21:20 ` Matt Carlson
2007-07-03 0:21 ` Michael Chan
2007-07-03 13:26 ` jamal
2007-07-04 4:19 ` Krishna Kumar2
2007-07-04 13:22 ` jamal
2007-07-03 13:09 ` jamal
2007-07-03 19:31 ` Matt Carlson
2007-07-04 1:59 ` jamal
2007-07-03 21:30 ` David Miller
2007-06-19 22:28 ` [WIP][PATCHES] Network xmit batching David Miller
2007-06-21 15:54 ` jamal [this message]
2007-06-21 16:08 ` FSCKED clock sources WAS(Re: " jamal
2007-06-21 16:55 ` Benjamin LaHaise
2007-06-25 16:59 ` jamal
2007-06-25 17:08 ` Benjamin LaHaise
2007-06-25 17:16 ` jamal
2007-06-21 16:45 ` Evgeniy Polyakov
2007-06-25 16:58 ` jamal
2007-06-19 16:24 ` jamal
2007-06-21 21:00 ` Rick Jones
2007-06-22 9:59 ` Evgeniy Polyakov
2007-06-25 17:35 ` Rick Jones
2007-06-07 8:42 ` Krishna Kumar2
2007-06-07 12:16 ` jamal
2007-06-08 5:06 ` Krishna Kumar2
2007-06-08 11:14 ` jamal
2007-06-08 11:31 ` Krishna Kumar2
2007-06-08 11:43 ` jamal
2007-06-08 18:00 ` Rick Jones
2007-06-08 17:27 ` Rick Jones
2007-06-09 0:17 ` jamal
2007-06-09 0:40 ` Rick Jones
2007-06-07 22:42 ` jamal
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=1182441257.5017.48.camel@localhost \
--to=hadi@cyberus.ca \
--cc=Robert.Olsson@data.slu.se \
--cc=davem@davemloft.net \
--cc=gaagaan@gmail.com \
--cc=johnpol@2ka.mipt.ru \
--cc=krkumar2@in.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=sri@us.ibm.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).