All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Rus V. Brushkoff" <rus@domain.hid>
Cc: Xenomai help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Deprecated kernel system calls in xenomai-head and new application development paradigm
Date: Wed, 02 Sep 2009 16:41:59 +0200	[thread overview]
Message-ID: <4A9E8437.80900@domain.hid> (raw)
In-Reply-To: <Pine.LNX.4.64.0909021611170.22914@domain.hid>

Rus V. Brushkoff wrote:
> On Wed, 2 Sep 2009, Philippe Gerum wrote:
> 
> :>  Next - I do not 
> :> understand why the previous model lets the _developer_ itself decide 
> :> which of the application tasks will be running in kernel and which will 
> :> be running in user space. The current model left the people without any 
> :> choice. So the current model itself decided instead of developer what is 
> :> better - I think this is wrong.
> :
> :With that kind of reasoning, you would keep on coding your RT
> :application fully in kernel space, but we made some progress since 1997,
> :fortunately.
> 
>  Sorry, but device drivers for hardware that need RT processing can't be 
> written in user space. Dealing with interrupts, PCI, DMA, I/O ports can 
> be done only in kernel space. So it is not possible to decide at the 
> Xenomai architect level wich driver task are optimal to run in which mode 
> - it will depends from the particular development problem area.
>  So I think that forcing people to write the RT tasks only in user space 
> will make unneded latencies, which will be inserted by data passing 
> between user and kernel domains.
>  Next: the traditional and clean Unix programming concept suppose that 
> user space applications are simple and operate on the files/pipes that 
> are attached to kernel drivers. It will be better to leave this concept 
> live as it proved its architect efficiency.

You misunderstand us. We tell you that you should develop drivers in
kernel-space, using the RTDM skin. The RTDM skin is made to resemble the
Linux driver model, so that it will make your drivers easily portable to
vanilla linux.


-- 
                                          Gilles



  parent reply	other threads:[~2009-09-02 14:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02  9:25 [Xenomai-help] Deprecated kernel system calls in xenomai-head and new application development paradigm Rus V. Brushkoff
2009-09-02  9:28 ` Gilles Chanteperdrix
2009-09-02  9:32   ` Rus V. Brushkoff
2009-09-02  9:34   ` Rus V. Brushkoff
2009-09-02 10:48     ` Gilles Chanteperdrix
2009-09-02 11:11       ` Rus V. Brushkoff
2009-09-02 11:16         ` Gilles Chanteperdrix
2009-09-02 11:25           ` Rus V. Brushkoff
2009-09-02 11:37             ` Gilles Chanteperdrix
2009-09-02 12:00               ` Rus V. Brushkoff
2009-09-02 12:41                 ` Philippe Gerum
2009-09-02 14:34                   ` Rus V. Brushkoff
2009-09-02 14:40                     ` Philippe Gerum
2009-09-02 14:41                     ` Gilles Chanteperdrix [this message]
2009-09-02 11:54             ` Philippe Gerum
2009-09-02 12:04               ` Rus V. Brushkoff
2009-09-02 12:25                 ` Philippe Gerum
2009-09-02 12:35                 ` 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=4A9E8437.80900@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=rus@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.