All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Isaac Griswold-Steiner <isaac.griswold.steiner@gmail.com>
Cc: williams@redhat.com, jkacur@redhat.com,
	linux-rt-users@vger.kernel.org, joshc@ni.com,
	Isaac Griswold-Steiner <isaac.griswoldsteiner@ni.com>
Subject: Re: [PATCH RFC] rdtscbench: a nohz_full validation and benchmarking tool
Date: Fri, 11 Dec 2015 17:26:07 +0100	[thread overview]
Message-ID: <20151211162607.GD6720@linutronix.de> (raw)
In-Reply-To: <1440189958-6959-1-git-send-email-isaac.griswoldsteiner@ni.com>

* Isaac Griswold-Steiner | 2015-08-21 15:45:58 [-0500]:

>From: Isaac Griswold-Steiner <isaac.griswoldsteiner@ni.com>
>
>rdtscbench is a cyclictest-like tool that spawns a thread per cpu. Each thread
>measures the difference in cycle count (using the tsc) during the execution of a
>tight loop.
>
>This is a simple tool intended to be used for the validation of nohz_full CPU
>configurations. As the validation of nohz_full CPUs is the objective, the tool
>avoids the usage of system calls, timers, or anything that might break nohz_full.
>
>Signed-off-by: Isaac Griswold-Steiner <isaac.griswoldsteiner@ni.com>

jkacur, williams: did you guys took a look on it?

Sebastian

  reply	other threads:[~2015-12-11 16:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21 20:45 [PATCH RFC] rdtscbench: a nohz_full validation and benchmarking tool Isaac Griswold-Steiner
2015-12-11 16:26 ` Sebastian Andrzej Siewior [this message]
2015-12-11 16:44   ` Clark Williams
2015-12-11 20:40 ` Clark Williams
     [not found]   ` <CAGt1KTzAuFcOez1mq9m1Cs7=dEOyS_Q8aBNfjfdx_x_2Mg0ePg@mail.gmail.com>
2015-12-18 15:40     ` Clark Williams
2015-12-21 13:15       ` John Kacur
2015-12-23 20:26         ` Isaac Griswold-Steiner
2015-12-23 20:43         ` [PATCH v2 " Isaac Griswold-Steiner

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=20151211162607.GD6720@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=isaac.griswold.steiner@gmail.com \
    --cc=isaac.griswoldsteiner@ni.com \
    --cc=jkacur@redhat.com \
    --cc=joshc@ni.com \
    --cc=linux-rt-users@vger.kernel.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.