public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "Turgis, Frederic" <f-turgis@ti.com>
To: Mark Wielaard <mjw@redhat.com>
Cc: "systemtap@sourceware.org" <systemtap@sourceware.org>
Subject: RE: Making the transport layer more robust
Date: Thu, 25 Aug 2011 12:12:00 -0000	[thread overview]
Message-ID: <13872098A06B02418CF379A158C0F1460162DC0A08@dnce02.ent.ti.com> (raw)
In-Reply-To: <1313500965.3393.5.camel@springer.wildebeest.org>

Hi,

These changes are relevant to http://sources.redhat.com/ml/systemtap/2011-q1/msg00179.html where we were trying to list the source/rate of recurrent wake-ups in the tool, that would "damage" Power Management activities on ARM (we use systemtap 80% profiling/20% debug)

So there can be some interest in sharing some thoughts on this as this impacts PM related to control channel:

- before changes:
* userspace (staprun/mainloop.c): we poll "control channel" (cmd channel) through non blocking read every 250ms
* kernel space (transport/control.c):
   + we periodically check for IO (_stp_ctl_ready_q not empty) or exit, through timer (used to be work queue)
   + periodic check for IO is in fact for cmd messages that don't announce themselves (STP_OOB_DATA for ex), i.e. are not allowed to wake-up "control wait queue" after we update _stp_ctl_ready_q. Other cmd messages would not need this check.

However, polling in both spaces looked redundant (we had not seen the "exit" at that time) so we have experimented first to set userspace polling to 2s and removed kernel space polling: tool runs fine but at next start, it needs to unload module before reloading it ("exit" issue)

=> long polling delay works OK, kernel periodic check for IO seems redundant with userspace but kernel polling for exit is needed


- after changes:
* userspace: we use "pselect" if supported. Great !
* kernel space:
   + polling for exit is still needed
   + polling for IO:
      * for cmd messages that don't announce themselves -> now mandatory otherwise pselect() would not return
      * for other cmd messages, it still does not look needed but there is no added value in differentiating them from above messages as we must do polling

=> we will experiment with this version playing only with the delay between 2 pollings (STP_CTL_TIMER_INTERVAL)


This will be a good occasion to reopen the PM topic with more experience from usage

Regards
Fred

Frederic Turgis
OMAP Platform Business Unit - OMAP System Engineering - Platform Enablement



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:[~2011-08-25 12:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-19  8:59 Mark Wielaard
2011-07-19 11:42 ` Mark Wielaard
2011-07-19 15:03 ` Mark Wielaard
2011-07-20  8:29   ` Mark Wielaard
2011-07-19 15:05 ` William Cohen
2011-07-20 14:13 ` Mark Wielaard
2011-07-21 17:18 ` David Smith
2011-08-12 17:43 ` Mark Wielaard
2011-08-15  8:24   ` Mark Wielaard
2011-08-15 18:30   ` Josh Stone
2011-08-16 13:23     ` Mark Wielaard
2011-08-25 12:12       ` Turgis, Frederic [this message]
2011-08-26 15:45         ` Turgis, Frederic
2011-08-26 18:45           ` Frank Ch. Eigler
2011-08-29  8:32             ` Turgis, Frederic
2011-08-29 11:21               ` Frank Ch. Eigler
2011-08-29 14:46               ` Frank Ch. Eigler
2011-08-30 13:20                 ` Turgis, Frederic
2011-09-05 11:27         ` Mark Wielaard
2011-09-05 14:32           ` Turgis, Frederic
     [not found]           ` <13872098A06B02418CF379A158C0F1460163182604@dnce02.ent.ti.com>
2011-09-06 10:12             ` Mark Wielaard
2011-09-06 14:30               ` Turgis, Frederic
2011-09-06 14:37               ` David Smith
2011-09-06 15:37                 ` David Smith
2011-09-06 16:25                   ` 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=13872098A06B02418CF379A158C0F1460162DC0A08@dnce02.ent.ti.com \
    --to=f-turgis@ti.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).