netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>,
	Robert.Olsson@data.slu.se,
	Stephen Hemminger <shemminger@linux-foundation.org>,
	Patrick McHardy <kaber@trash.net>
Subject: fscked clock sources revisited
Date: Mon, 30 Jul 2007 21:10:39 -0400	[thread overview]
Message-ID: <1185844239.5162.17.camel@localhost> (raw)

Folks,

I have posted this before but got no good response and i havent had time
to chase it. 
While doing some batching tests with pktgen and then with a simple
client server app with udp, it does appear that the clock source used
matters. Here are some basic runs with plain vanilla 2.6.22-rc4 runs
with udp. There are five runs per clock source and each result is in
Mbps.

acpi_pm: 108, 110, 111,  91, 108
tsc:     143, 108, 161, 129, 108
jiffies: 132, 138, 132, 146, 150

jiffies produces better results than tsc which produces better results
than acpi_pm. 

Second issue: I cant consistently get two reboots to always boot with
the same clock source.

Any ideas whats going on here? I havent tried with latest tree.

PS:- These results are very easy to validate with iperf or netperf.

cheers,
jamal


             reply	other threads:[~2007-07-31  1:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31  1:10 jamal [this message]
2007-07-31  1:10 ` fscked clock sources revisited Arjan van de Ven
2007-07-31  1:17   ` jamal
2007-07-31  1:23     ` jamal
2007-07-31  2:07       ` Arjan van de Ven
2007-07-31  1:37 ` David Miller
2007-07-31  2:03   ` Arjan van de Ven
2007-07-31  2:14   ` jamal
2007-08-07 13:19     ` 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=1185844239.5162.17.camel@localhost \
    --to=hadi@cyberus.ca \
    --cc=Robert.Olsson@data.slu.se \
    --cc=davem@davemloft.net \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.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).