From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: mtk.manpages@gmail.com, Randy Dunlap <rdunlap@infradead.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: [patch] timer_stats, doc: Readout of /proc/timer_stats doesn't disable sampling
Date: Fri, 02 May 2014 12:13:10 +0200 [thread overview]
Message-ID: <53636FB6.9060407@gmail.com> (raw)
From: Michael Kerrisk <mtk.manpages@gmail.com>
Some simple testing shows that reading from /proc/timer_stats
does not disable sampling. Looking back over past source code,
it appears that it never did.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
---
Documentation/timers/timer_stats.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/timers/timer_stats.txt b/Documentation/timers/timer_stats.txt
index 8abd40b..de835ee 100644
--- a/Documentation/timers/timer_stats.txt
+++ b/Documentation/timers/timer_stats.txt
@@ -39,9 +39,9 @@ To stop a sample period issue:
The statistics can be retrieved by:
# cat /proc/timer_stats
-The readout of /proc/timer_stats automatically disables sampling. The sampled
-information is kept until a new sample period is started. This allows multiple
-readouts.
+While sampling is enabled, each readout from /proc/timer_stats will see
+newly updated statistics. Once sampling is disabled, the sampled information
+is kept until a new sample period is started. This allows multiple readouts.
Sample output of /proc/timer_stats:
--
1.9.0
next reply other threads:[~2014-05-02 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 10:13 Michael Kerrisk (man-pages) [this message]
2014-05-05 8:46 ` [tip:timers/core] timer_stats/doc: Fix /proc/ timer_stats documentation tip-bot for Michael Kerrisk
-- strict thread matches above, loose matches on Subject: below --
2014-05-02 9:29 [patch] timer_stats, doc: Readout of /proc/timer_stats doesn't disable sampling Michael Kerrisk (man-pages)
2014-05-02 9:37 ` Michael Kerrisk
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=53636FB6.9060407@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rdunlap@infradead.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