From: Jan Kiszka <jan.kiszka@domain.hid>
To: Steven Seeger <sseeger@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] overhead
Date: Mon, 11 Feb 2008 18:02:28 +0100 [thread overview]
Message-ID: <47B07FA4.8050801@domain.hid> (raw)
In-Reply-To: <51CAD0CE1504444DBE77CBBE51A0135D376ADB@slcmail.slc.mew.int>
Steven Seeger wrote:
> The overhead was measured by only comparing cpu usage between tasks from
> the statistics collection stuff. There are some userland tasks running
> at 8khz, so apparently this is a problem for Xenomai on this board. I
> had no problem at all with these tasks in kernel space under rtai.
>
> There are no faults at all under /proc/xenomai/faults.
>
> The main way I can tell something is wrong is that if my three fast
> tasks are running (8 khz in kernel space, 8 khz in userspace, and 50 hz
> in userspace) then a lower priority task will timeout and trip a
> watchdog. If I remove the IO routines from the 50hz task, then the
> others can still run.
I/O does not come for free (specifically on ISA HW - if that is the case
for you). But if you think that this makes a difference here, what about
measuring both kernel- and userland-based I/O accesses in a loop and
compare the runtime? This would also allow you to quantify the impact -
regardless if there is a difference or not.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2008-02-11 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 6:04 [Xenomai-help] overhead Steven Seeger
2008-02-11 13:54 ` Jan Kiszka
2008-02-11 15:20 ` Steven Seeger
2008-02-11 16:10 ` Gilles Chanteperdrix
2008-02-11 17:43 ` Steven Seeger
2008-02-11 17:58 ` Jan Kiszka
2008-02-11 18:59 ` Philippe Gerum
2008-02-11 19:16 ` Steven Seeger
2008-02-11 20:11 ` Philippe Gerum
2008-02-11 20:18 ` Steven Seeger
2008-02-11 17:02 ` Jan Kiszka [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=47B07FA4.8050801@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=sseeger@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.