public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "Turgis, Frederic" <f-turgis@ti.com>
To: Josh Stone <jistone@redhat.com>
Cc: Mark Wielaard <mjw@redhat.com>,
	"Frank Ch. Eigler" <fche@redhat.com>,
	       "systemtap@sourceware.org" <systemtap@sourceware.org>
Subject: RE: Tune reader_thread poll timeout value
Date: Thu, 03 May 2012 00:15:00 -0000	[thread overview]
Message-ID: <28BE1A38672C8B4481BB423D0FD1F22E18F566F9@DNCE04.ent.ti.com> (raw)
In-Reply-To: <4FA19BDD.60605@redhat.com>

>That's an important point, that this tunable as you've implemented it is
>built into stapio, not into individual modules, so it's much more
>static.  Maybe this would be better as a command-line option to
>staprun/stapio?  (like the current -b buffer size)

For most people, this tunable is a low-importance item/corner case quite specific to TI so this is why we did not intend to expose it to command line, which is generally more generic and key things to play with.
Thinking about this, we generally prefer high timeout value for Power Management considerations except for "probe timer.s(x)" scripts like iotop.stp where it is interesting to see directly the output. Still, setting tunable to something like 2s would make everyone happy on our side so we would not play with different values on the fly.

But if systemtap experts feel it is worth exposing it like -b option, we will of course patch accordingly, this would be the most flexible solution !

Regards
Fred

Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve Loubet. 036 420 040 R.C.S Antibes. Capital de EUR 753.920



  reply	other threads:[~2012-05-03  0:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-01 20:10 Turgis, Frederic
2012-05-01 21:30 ` Frank Ch. Eigler
2012-05-02  8:46 ` Mark Wielaard
2012-05-02 19:39   ` Turgis, Frederic
2012-05-02 20:41     ` Josh Stone
2012-05-03  0:15       ` Turgis, Frederic [this message]
2012-05-03  8:33         ` Mark Wielaard
2012-05-07 11:52         ` Turgis, Frederic
2012-05-07 13:56           ` Frank Ch. Eigler
2012-05-07 16:09             ` Turgis, Frederic
2012-05-14 23:59               ` Turgis, Frederic
2012-05-15 14:25                 ` Frank Ch. Eigler
2012-05-15 15:29                   ` Turgis, Frederic
2012-05-22 17:53                     ` Turgis, Frederic

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=28BE1A38672C8B4481BB423D0FD1F22E18F566F9@DNCE04.ent.ti.com \
    --to=f-turgis@ti.com \
    --cc=fche@redhat.com \
    --cc=jistone@redhat.com \
    --cc=mjw@redhat.com \
    --cc=systemtap@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).