From: Andreas Glatz <andreasglatz@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>, xenomai@xenomai.org
Subject: Re: [Xenomai-help] Running out of stack memory in kernel-space
Date: Thu, 28 May 2009 13:58:50 -0400 [thread overview]
Message-ID: <1243533530.898.36.camel@domain.hid> (raw)
In-Reply-To: <1243529533.22173.6.camel@domain.hid>
On Thu, 2009-05-28 at 18:52 +0200, Philippe Gerum wrote:
> On Thu, 2009-05-28 at 11:59 -0400, Andreas Glatz wrote:
> > Hi,
> >
> > We have to start 40+ Xenomai tasks in kernel space.
>
> Why subjecting yourself to the pain of running a complex application in
> kernel space? The difference between kernel and userland latencies on an
> mpc836x should not be worth it.
>
We see a 70us difference between running exactly the same
application in kernel-space and user-space. The application
registers the rx and tx interrupt of one UEC and replaces
the buffer descriptor rings allocated by Linux, and
takes care of the buffer handling. During the
test we send out an Ethernet frame from the MPC8360, the
frame gets processed on the other end of the wire and
eventually we receive the response from the other device.
The total round trip time (function call send() to
return of function call receive() measured with __xn_rdtsc())
is 230us in kernel-space and 300us in user-space.
FYI: Another device which used direct SMI instead of Ethernet
to talk to the device on the other end of the wire showed a
round trip time of 40us...
Andreas
next prev parent reply other threads:[~2009-05-28 17:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 15:59 [Xenomai-help] Running out of stack memory in kernel-space Andreas Glatz
2009-05-28 16:39 ` Philippe Gerum
2009-05-28 18:23 ` Andreas Glatz
2009-05-28 22:14 ` Philippe Gerum
2009-05-28 16:52 ` Philippe Gerum
2009-05-28 17:58 ` Andreas Glatz [this message]
2009-05-28 21:47 ` Philippe Gerum
2009-06-22 13:23 ` Andreas Glatz
2009-06-23 9:30 ` Philippe Gerum
2009-06-23 9:37 ` Gilles Chanteperdrix
2009-06-23 10:23 ` Philippe Gerum
2009-06-23 10:37 ` Philippe Gerum
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=1243533530.898.36.camel@domain.hid \
--to=andreasglatz@domain.hid \
--cc=rpm@xenomai.org \
--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.