All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Nilanjan Roychowdhury <Nilanjan.Roychowdhury@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] driver migration
Date: Thu, 14 Sep 2006 11:40:47 +0200	[thread overview]
Message-ID: <4509239F.8000203@domain.hid> (raw)
In-Reply-To: <9D98C51005D80D43A19A3DF329A61D69515624@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]

Nilanjan Roychowdhury wrote:
>> Performance will remain a reason to go to kernel-space, specifically if
>> you either share your device between multiple processes (having a
> driver
>> in a separate process comes at a price...) or if you need low latency
> on
>> IRQ handling. But there are also reasons to go to user-space, e.g.
>> license issues. We are trying to address both.
> 
> Nilanjan :- Can I assume you are saying the latency is less when I run
> my interrupt processing code as an real time ISR rather than a user -
> space 
> Thread ?

Yes, of course. Check the irqbench test for real numbers on your target
system.

> In that case I can run the ISR in kernel mode and signal the user space
> RT task by a semaphore ( the user space task will bind this).

That would be the classic design if you have some simple job to do on
IRQ delivery (some direct fiddling with the hardware e.g.) + you want to
wakeup a thread waiting on the event. In this case you can use RTDM for
the in-kernel part and attach your application to the RTDM device your
driver will then export.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2006-09-14  9:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14  9:37 [Xenomai-help] driver migration Nilanjan Roychowdhury
2006-09-14  9:40 ` Jan Kiszka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-14  9:52 Nilanjan Roychowdhury
2006-09-14 10:40 ` Jan Kiszka
2006-09-14  9:10 Nilanjan Roychowdhury
2006-09-14  9:27 ` Jan Kiszka

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=4509239F.8000203@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=Nilanjan.Roychowdhury@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.