From: Raz <raziebe@gmail.com>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: hpet0 versus hpet2
Date: Sun, 29 Jun 2014 15:49:31 +0300 [thread overview]
Message-ID: <CAPB=Z-q3HyP7W3Env8m=VELPMfBhRhAQwmfPyT3G9_9PQhFW2w@mail.gmail.com> (raw)
Hey Rt folks
I performed a benchmark that compares the jitter of hpet2 to hpet0.
hpet0 is reserved to the kernel use ( hpet_reserve_timer(&hd, 0).
and hd.hd_irq[0] = HPET_LEGACY_8254; in arch/x86/kernel/hpet.c).
I removed these two lines.
The bellow is a histogram compares the default hpet2 to hpet0 in atom D525.
The test performed is a simple udp sender, it sends a single udp
packet each 1ms interval.
Time stamping were made by Beckhoff ET2000 ,so that the timestamps
taken by a reliable and accurate tool.
Question is whether it is possible to push a new kernel boot command
line option that gives
the user hpet0 ?
hpet0
-50 0
-40 0
-20 2
-10 14
-5 143
-1 3992
1 95217
5 544
10 74
20 14
30 0
40 0
50 0
More 0
hpet2
Bin Frequency
-50 1
-40 0
-20 0
-10 0
-5 0
-1 1
1 18
5 71
10 854
20 93098
30 237
40 1069
50 0
More 0
reply other threads:[~2014-06-29 12:49 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='CAPB=Z-q3HyP7W3Env8m=VELPMfBhRhAQwmfPyT3G9_9PQhFW2w@mail.gmail.com' \
--to=raziebe@gmail.com \
--cc=linux-rt-users@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).