From: Wolfgang Denk <wd@denx.de>
To: brian.auld@adic.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Kernel Preemption patch
Date: Mon, 24 Feb 2003 22:15:43 +0100 [thread overview]
Message-ID: <20030224211548.0DA99C6E0C@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 24 Feb 2003 05:47:35 PST." <995FF289C9D69747A09E42992644595405B23683@penguin.adic.com>
In message <995FF289C9D69747A09E42992644595405B23683@penguin.adic.com> you wrote:
>
> - I presume RTAI and subsequently any task running on top of it are running
> in user mode, as opposed to kernel mode?
Wrong. The real-time part of RTAI applications usually runs in kernel
mode; it may (but does not have to) communicate with user-land
applications.
> - Would it be possible, using the RTAI, to receive inbound data encapsulated
> in some storage protocal via the associate device driver, pass this about
> a few RTAI tasks, and then ship it out encapsualted in another storage
> protocal envelope via the associate device driver ... all the time using
> the same buffer of I/O data (i.e. no buffer to buffer copies)??
Sure.
> Given our need to prevent buffer copies of I/O data, I was envisioning
> implementing a good part of our application as kernel treads. This is why I
> was looking into the preemption patch, and also why Real-Time abastraction
> layers that sit on top of the kernel were not showing up on my radar.
RTAI does not sit on top of linux, it's rather vice versa: Linux sits
on top of the RTAI "real-time kernel".
F'up to <rtai@rtai.org> ?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
If a train station is a place where a train stops,
then what's a workstation?
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2003-02-24 21:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <995FF289C9D69747A09E42992644595405B23683@penguin.adic.com>
2003-02-24 21:15 ` Wolfgang Denk [this message]
2003-02-25 14:32 Kernel Preemption patch brian.auld
2003-02-26 4:14 ` Matt Porter
-- strict thread matches above, loose matches on Subject: below --
2003-02-24 20:45 brian.auld
2003-02-24 22:29 ` Eugene Surovegin
2003-02-25 9:12 ` Stefan Roese
2003-02-25 13:24 ` Matt Porter
2003-02-26 4:18 ` Matt Porter
2003-02-26 4:25 ` Eugene Surovegin
2003-02-26 4:52 ` Matt Porter
2003-02-24 15:56 brian.auld
2003-02-24 18:02 ` Eugene Surovegin
2003-02-24 19:06 ` Todd Poynor
2003-02-24 15:38 brian.auld
2003-02-24 18:05 ` Eugene Surovegin
2003-02-24 18:50 ` Matt Porter
2003-02-24 12:54 brian.auld
2003-02-23 22:28 brian.auld
2003-02-23 22:33 ` Allen Curtis
2003-02-23 22:54 ` Eugene Surovegin
2003-02-23 23:05 ` Eugene Surovegin
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=20030224211548.0DA99C6E0C@atlas.denx.de \
--to=wd@denx.de \
--cc=brian.auld@adic.com \
--cc=linuxppc-embedded@lists.linuxppc.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 NNTP newsgroup(s).