From: John Kacur <jkacur@redhat.com>
To: Piotr Gregor <piotrgregor@rsyncme.org>
Cc: Clark Williams <williams@redhat.com>, linux-rt-users@vger.kernel.org
Subject: Re: Calculate average latencies on the fly
Date: Wed, 16 Nov 2016 15:47:47 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.20.1611161525280.12617@riemann.fritz.box> (raw)
In-Reply-To: <CAK+oA4WFAaT4DmR=8nKqTsyKe9imDYCu5p6DG4kqbhoBPD=LXw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
Please inline the patches
There are 1000000 microseconds / second, the default interval is 1000us,
but let's say we did it more frequently at 100us
1000000 us / 100 intervals = 10000 samples / second * 60 sec/min * 60
min/hr * 24 hrs/day * 365 days / year * 1000 (very pessimistic diff) =
an accumulated diff of 3.1536×10^14
With a max double of 9x10^15/3.15*10^14 we could run for 30 years before
we move into normal numbers.
So, the problem with your patch, is not just the problem which it proposes
to fix, is one I see as mostly theoretical, but there is the potential for
accumulating small inaccuracies.
Of course, there is always the chance that I made some kind of error in my
analysis here, please feel free to point it out!
What might be more interesting is how long would it take for the cycles to
overflow?
Thanks
John
On Mon, 14 Nov 2016, Piotr Gregor wrote:
> There was an error in previous patch. Please find attached corrected patch.
>
> cheers,
> Piotr
>
next prev parent reply other threads:[~2016-11-16 14:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 10:00 Calculate average latencies on the fly Piotr Gregor
2016-11-14 11:50 ` Piotr Gregor
2016-11-14 15:42 ` Mathieu Poirier
2016-11-14 16:11 ` Piotr Gregor
2016-11-14 16:58 ` Clark Williams
2016-11-16 14:47 ` John Kacur [this message]
2016-11-19 23:27 ` Piotr Gregor
2016-11-20 5:03 ` Tracy Smith
2016-11-21 18:32 ` John Kacur
[not found] ` <CAChUvXOj_D2N3o7BoEUjt1A1O0fXZnvGSz5ba=O55h12ns___A@mail.gmail.com>
2016-11-22 15:43 ` John Kacur
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=alpine.LFD.2.20.1611161525280.12617@riemann.fritz.box \
--to=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=piotrgregor@rsyncme.org \
--cc=williams@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.