From: Richard Cochran <richardcochran@gmail.com>
To: John Stultz <john.stultz@linaro.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Miroslav Lichvar <mlichvar@redhat.com>,
Prarit Bhargava <prarit@redhat.com>
Subject: Re: [PATCH] [RFC] timekeeping: Rework frequency adjustments to work better w/ nohz
Date: Mon, 13 Jan 2014 18:51:16 +0100 [thread overview]
Message-ID: <20140113175114.GA4271@netboy> (raw)
In-Reply-To: <1389067023-13541-1-git-send-email-john.stultz@linaro.org>
On Mon, Jan 06, 2014 at 07:57:03PM -0800, John Stultz wrote:
>
> I still think this is probably 3.15 or later material, but I'd be
> very interested in feedback, thoughts, and testing.
Over the weekend I did a short test of this new approach. I compiled
two kernels, one plain v3.12.7 and one with the proposed fix. The
test was run on three different kernel variants, the current nohz
kernel, the same with nohz=off, and the same but with John's patch.
I used a simple test script (see below). Using a PCIe express card as
a PHC, the Intel Corporation 82574L, I simply let the this clock run
free (not sync'ed to gps or anything), and then synchronized the Linux
system clock to the PHC using the phc2sys program with a sample rate
of once every 32 seconds. Each of the tests ran for at least three
hours on a system without any other load.
- Linux 3.12.7-nohz-plain-20140106 nohz-plain.log
- Linux 3.12.7-nohz-plain-20140106 NOHZ=OFF periodic-plain.log
- Linux 3.12.7-nohz-fix-20140106-00001-gd753140 nohz-fix.log
The performance in the log files as reflected in the clock offset is
summarized in this table. The values are in nanoseconds.
| | periodic-plain | nohz-fix | nohz-plain |
|---------+----------------+---------------+---------------|
| minimum | -1.599000e+03 | -1.051000e+03 | -5.373700e+04 |
| maximum | +1.311000e+03 | +1.048000e+03 | +6.389500e+04 |
| mean | +9.880240e-02 | -7.747305e+01 | +1.597904e+01 |
| stddev | +4.610021e+02 | +3.960978e+02 | +1.491263e+04 |
I also made two graphs.
http://linuxptp.sourceforge.net/nohz-fix/current_nohz.png
http://linuxptp.sourceforge.net/nohz-fix/periodic_vs_fix.png
(The log files and scripts are also in that directory.)
So in this test, it looks like the new approach performed at least as
well as using regular, periodic ticks.
Thanks,
Richard
---
# nohz-fix-testing.sh
#
# set the ptp clock time from the system time
#
./testptp -s; ./testptp -g; date
#
# wait a bit to let the clocks drift
#
sleep 10
#
# start the servo
#
./phc2sys -s eth4 -m -q -l7 -O0 -P0 -I0 -R.03125
next prev parent reply other threads:[~2014-01-13 17:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 3:57 [PATCH] [RFC] timekeeping: Rework frequency adjustments to work better w/ nohz John Stultz
2014-01-13 17:51 ` Richard Cochran [this message]
2014-01-13 18:15 ` John Stultz
2014-01-14 7:07 ` Richard Cochran
2014-01-28 17:58 ` Richard Cochran
2014-01-29 17:56 ` John Stultz
2014-02-07 11:45 ` Miroslav Lichvar
2014-02-07 18:21 ` John Stultz
2014-02-12 15:42 ` Miroslav Lichvar
2014-04-24 4:22 ` John Stultz
2014-04-24 11:28 ` Miroslav Lichvar
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=20140113175114.GA4271@netboy \
--to=richardcochran@gmail.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlichvar@redhat.com \
--cc=prarit@redhat.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).