public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: Clark Williams <williams@redhat.com>,
	John Kacur <jkacur@redhat.com>,
	linux-rt-users@vger.kernel.org, psahoo@redhat.com
Subject: Re: [rt-tests v1 6/6] oslat: Use parse_cpumask() from rt-numa.h
Date: Wed, 10 Feb 2021 11:07:45 -0500	[thread overview]
Message-ID: <20210210160745.GH103365@xz-x1> (raw)
In-Reply-To: <20201113210910.21807-7-dwagner@suse.de>

On Fri, Nov 13, 2020 at 10:09:10PM +0100, Daniel Wagner wrote:
> Use the common parse_cpumask() helper and use struct bitmask directly
> instead transforming it into a CPU_SET first.
> 
> Signed-off-by: Daniel Wagner <dwagner@suse.de>

Hi, Daniel,

This seems to have broken oslat with --cpu-list...

xz-x1:rt-tests [master]$ sudo ./oslat -c 1-2
Total runtime:          1 seconds
Thread priority:        default
CPU list:               1-2
CPU for main thread:    0
Workload:               no
Workload mem:           0 (KiB)
Preheat cores:          1

Pre-heat for 1 seconds...
Test starts...
Test completed.

        Core:    1
    CPU Freq:    2114 (Mhz)
    001 (us):    49979990
    002 (us):    471
    003 (us):    53
    004 (us):    9
    005 (us):    16
    006 (us):    14
    007 (us):    4
    008 (us):    4
    009 (us):    1
    010 (us):    1
    011 (us):    0
    012 (us):    0
    013 (us):    2
    014 (us):    59
    015 (us):    11
    016 (us):    173
    017 (us):    12
    018 (us):    25
    019 (us):    112
    020 (us):    10
    021 (us):    66
    022 (us):    7
    023 (us):    13
    024 (us):    16
    025 (us):    7
    026 (us):    18
    027 (us):    13
    028 (us):    7
    029 (us):    3
    030 (us):    3
    031 (us):    0
    032 (us):    5 (including overflows)
     Minimum:    1 (us)
     Average:    1.000 (us)
     Maximum:    82 (us)
     Max-Min:    81 (us)
    Duration:    0.995 (sec)

Reported-by: Pradipta Kumar Sahoo <psahoo@redhat.com>

Thanks,

-- 
Peter Xu


  parent reply	other threads:[~2021-02-10 16:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 21:09 [rt-tests v1 0/6] Move common code to helper libraries Daniel Wagner
2020-11-13 21:09 ` [rt-tests v1 1/6] rt-utils: Introduce parse_mem_string() Daniel Wagner
2020-11-18 20:59   ` John Kacur
2020-11-13 21:09 ` [rt-tests v1 2/6] oslat: Use string parser utilies Daniel Wagner
2020-11-18 21:00   ` John Kacur
2020-11-13 21:09 ` [rt-tests v1 3/6] cyclictest: Remove deadcode checking for NUMA Daniel Wagner
2020-11-18 21:01   ` John Kacur
2020-11-13 21:09 ` [rt-tests v1 4/6] rt-numa: Introduce NUMA helpers Daniel Wagner
2020-11-18 21:09   ` John Kacur
2020-11-19  8:21     ` Daniel Wagner
2020-11-13 21:09 ` [rt-tests v1 5/6] cyclictest: Use parse_cpumask() from rt-numa.h Daniel Wagner
2020-11-18 21:10   ` John Kacur
2020-11-18 21:17   ` John Kacur
2020-11-13 21:09 ` [rt-tests v1 6/6] oslat: " Daniel Wagner
2020-11-18 21:18   ` John Kacur
2021-02-10 16:07   ` Peter Xu [this message]
2021-02-10 16:29     ` Daniel Wagner

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=20210210160745.GH103365@xz-x1 \
    --to=peterx@redhat.com \
    --cc=dwagner@suse.de \
    --cc=jkacur@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=psahoo@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox