All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [PATCH 0/3] Reworked nucleus statistics
Date: Fri, 27 Oct 2006 18:00:23 +0200	[thread overview]
Message-ID: <1161964824.4983.0.camel@domain.hid> (raw)
In-Reply-To: <452E9ACD.20800@domain.hid>

On Thu, 2006-10-12 at 21:43 +0200, Jan Kiszka wrote:
> Hi,
> 
> here we go: after quite some hacking and refactoring, Dmitry and I are
> happy to provide a patch set that reworks and enhances the statistics
> subsystem of Xenomai.
> 
> The original goal of these patches was to improve the accuracy of the
> /proc/xenomai/stat CPU load output. So far it only accounted thread
> switches. The time of potential preceding IRQ handling and scheduling
> decision was added to the preempted thread. The new approach avoids
> this. More about it later.
> 
> While discussing the first implementation, Dmitry had the idea to
> refactor even more code that depends on XENO_OPT_STATS, means event
> counting parts under the upcoming generic runtime stats. So this series
> starts with a patch to introduce a generic subsystem for collecting
> statistics on countable events as well as the runtime of entities.
> 
> It continues with the second patch that applies xnstat on the IRQ
> subsystem, both for counting hits as well as for measuring the execution
> time. The accounting model applied in this patch is as simple as this:
> measure the time some driver- or application-supplied ISR executes and
> accumulate it per-CPU. The rescheduling is still accounted to the
> preempted thread.
> 
> In my endless quest for perfection, I applied an -as I feel- enhanced
> model on top of this (already working!) set, that's the third patch.
> This model adds the scheduler path to the IRQ account. And it only
> accounts to an IRQ if its ISR reported XN_ISR_HANDLED. This is relevant
> for shared IRQs when only one source fired (the typical case). Also, it
> reduces churning by avoiding account switches in the average case. But,
> the downside, it may be less convenient to understand and increases the
> code a bit (only for the shared IRQ case). Dmitry and I were not yet
> able to agree on THE model, so I'm simply posting both for public
> feedback. :)

All merged, thanks.

-- 
Philippe.




      parent reply	other threads:[~2006-10-27 16:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-12 19:43 [Xenomai-core] [PATCH 0/3] Reworked nucleus statistics Jan Kiszka
2006-10-18 13:42 ` Philippe Gerum
2006-10-18 20:06   ` Dmitry Adamushko
2006-10-18 20:29     ` Jan Kiszka
2006-10-19  9:59       ` Dmitry Adamushko
2006-10-19 20:53     ` Philippe Gerum
2006-10-27 16:00 ` Philippe Gerum [this message]

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=1161964824.4983.0.camel@domain.hid \
    --to=rpm@xenomai.org \
    --cc=jan.kiszka@domain.hid \
    --cc=xenomai@xenomai.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 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.