From: David Sommerseth <davids@redhat.com>
To: Clark Williams <williams@redhat.com>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
John Kacur <jkacur@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
RT <linux-rt-users@vger.kernel.org>
Subject: Re: RFC: patch to trigger thread stats output from cyclictest with SIGHUP
Date: Mon, 11 Mar 2013 17:54:05 +0100 [thread overview]
Message-ID: <513E0C2D.1050401@redhat.com> (raw)
In-Reply-To: <CAP=VYLrV7QbA_+L66WVGSYoJaF-+sh8uyw0boq8hDCkF0xrQtw@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/03/13 17:25, Paul Gortmaker wrote:
> On Mon, Mar 11, 2013 at 12:16 PM, Clark Williams
> <williams@redhat.com> wrote:
>> John,
>>
>> Steven suggested a feature for cyclictest that I'd actually been
>> whining about (internally anyway). During long rteval runs
>> there's really no feedback available if you want to know how the
>> run is progressing. Steven suggested sending SIGHUP and dumping
>> the current state. Below is a patch that seems to work for
>> cyclictest; just wanted to get some feedback on whether this
>> would be acceptable behaviour.
>
> Is USR1 already in use for something? That would be consistent
> with how things like dd use USR1 signal - to report interim stats.
>
> P.
+1 ... I was just about to say exactly the same.
- --
kind regards,
David Sommerseth
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlE+DCsACgkQIIWEatLf4Hc4lACdHs1Cuv4u1tJxkoDOfmKXSCiL
s/gAn1XHwrcn2jiNF2Q+0EC22aj+j1Ah
=nME1
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-03-11 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 16:16 RFC: patch to trigger thread stats output from cyclictest with SIGHUP Clark Williams
2013-03-11 16:25 ` Paul Gortmaker
2013-03-11 16:54 ` David Sommerseth [this message]
2013-03-11 17:16 ` Clark Williams
2013-03-12 12:10 ` John Kacur
2013-03-12 13:43 ` Clark Williams
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=513E0C2D.1050401@redhat.com \
--to=davids@redhat.com \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=rostedt@goodmis.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.