public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] rt-tests: oslat: convert to nanoseconds correctly
@ 2024-02-01 17:50 Marcelo Tosatti
  2024-02-02 16:34 ` John Kacur
  0 siblings, 1 reply; 2+ messages in thread
From: Marcelo Tosatti @ 2024-02-01 17:50 UTC (permalink / raw)
  To: linux-rt-users; +Cc: Chuck Newman, John Kacur


With buckets of size 1us, accounting for measurements in the
[1ns, 999ns] range are done to the 2us bucket (while they 
should be accounted in the 1us bucket):

    001 (us):	0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    002 (us):	41916187 41937649 41938461 42029055 ...
    003 (us):	969 985 958 972 964 986 970 961 973 ...

Fix this by doing a plain cycles -> nanoseconds convertion:

    001 (us):	43287555 43086678 43087427 43109974 ...
    002 (us):	983 987 985 975 982 960 993 961 992 ...
    003 (us):	9 6 7 13 9 22 3 21 3 3 8 8 10 11 3 55


Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Reported-by: Chuck Newman <chuck.newman@hpe.com>

diff --git a/src/oslat/oslat.c b/src/oslat/oslat.c
index 4bdca64..13e887d 100644
--- a/src/oslat/oslat.c
+++ b/src/oslat/oslat.c
@@ -334,7 +334,7 @@ static void insert_bucket(struct thread *t, stamp_t value)
 	uint64_t extra;
 	double us;
 
-	lat = (value * g.unit_per_us + t->counter_mhz - 1) / t->counter_mhz;
+	lat = (value * g.unit_per_us) / t->counter_mhz;
 	us = (double)lat / g.unit_per_us;
 	if (!g.preheat && g.trace_threshold && us >= g.trace_threshold) {
 		char *line = "%s: Trace threshold (%d us) triggered on cpu %d with %.*f us!\n";


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] rt-tests: oslat: convert to nanoseconds correctly
  2024-02-01 17:50 [PATCH] rt-tests: oslat: convert to nanoseconds correctly Marcelo Tosatti
@ 2024-02-02 16:34 ` John Kacur
  0 siblings, 0 replies; 2+ messages in thread
From: John Kacur @ 2024-02-02 16:34 UTC (permalink / raw)
  To: Marcelo Tosatti; +Cc: linux-rt-users, Chuck Newman



On Thu, 1 Feb 2024, Marcelo Tosatti wrote:

> 
> With buckets of size 1us, accounting for measurements in the
> [1ns, 999ns] range are done to the 2us bucket (while they 
> should be accounted in the 1us bucket):
> 
>     001 (us):	0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
>     002 (us):	41916187 41937649 41938461 42029055 ...
>     003 (us):	969 985 958 972 964 986 970 961 973 ...
> 
> Fix this by doing a plain cycles -> nanoseconds convertion:
> 
>     001 (us):	43287555 43086678 43087427 43109974 ...
>     002 (us):	983 987 985 975 982 960 993 961 992 ...
>     003 (us):	9 6 7 13 9 22 3 21 3 3 8 8 10 11 3 55
> 
> 
> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
> Reported-by: Chuck Newman <chuck.newman@hpe.com>
> 
> diff --git a/src/oslat/oslat.c b/src/oslat/oslat.c
> index 4bdca64..13e887d 100644
> --- a/src/oslat/oslat.c
> +++ b/src/oslat/oslat.c
> @@ -334,7 +334,7 @@ static void insert_bucket(struct thread *t, stamp_t value)
>  	uint64_t extra;
>  	double us;
>  
> -	lat = (value * g.unit_per_us + t->counter_mhz - 1) / t->counter_mhz;
> +	lat = (value * g.unit_per_us) / t->counter_mhz;
>  	us = (double)lat / g.unit_per_us;
>  	if (!g.preheat && g.trace_threshold && us >= g.trace_threshold) {
>  		char *line = "%s: Trace threshold (%d us) triggered on cpu %d with %.*f us!\n";
> 
> 
> 
Signed-off-by: John Kacur <jkacur@redhat.com>


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2024-02-02 16:34 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-02-01 17:50 [PATCH] rt-tests: oslat: convert to nanoseconds correctly Marcelo Tosatti
2024-02-02 16:34 ` John Kacur

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox