From: Jan Kiszka <jan.kiszka@domain.hid>
To: Brandt Erickson <brandt@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] xnpod help
Date: Fri, 02 Jun 2006 00:55:07 +0200 [thread overview]
Message-ID: <447F704B.10303@domain.hid> (raw)
In-Reply-To: <47190.155.98.4.39.1149199741.squirrel@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
Brandt Erickson wrote:
>> Ok, things get clearer. But why a kernel module? Are you *that* short on
>> CPU cycles?
>
> The reason why I'm trying to develop a kernel-space application is not for
> latency issues but because I need to be in kernel-space to read/write
> to/from my DAC.
ioperm() or iopl() not applicable?
> Is the IPC between kernel-space realtime and user-space
> non-realtime that much more difficult the user-space realtime to
> user-space non-realtime? I've familiar with regular user-space IPC using
> condition variables, semaphores, and shared memory, so if it's fairly
> similar, I'm hoping that won't be a problem.
That's feasible as well, and the API is identical. It's just the
difference of writing two separate applications instead of a single
multi-threaded one plus the additional effort for dealing with modules
(building, loading, unloading).
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
next prev parent reply other threads:[~2006-06-01 22:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 18:20 [Xenomai-help] xnpod help Brandt Erickson
2006-06-01 19:06 ` Jan Kiszka
2006-06-01 19:56 ` Gilles Chanteperdrix
2006-06-01 20:10 ` Jan Kiszka
2006-06-01 20:51 ` Brandt Erickson
2006-06-01 21:16 ` Jan Kiszka
2006-06-01 22:09 ` Brandt Erickson
2006-06-01 22:55 ` Jan Kiszka [this message]
2006-06-02 20:41 ` Brandt Erickson
2006-06-03 8:26 ` Jan Kiszka
2006-06-02 12:53 ` Gilles Chanteperdrix
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=447F704B.10303@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=brandt@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.