All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stéphane ANCELOT" <sancelot@domain.hid>
To: "M. Koehrer" <mathias_koehrer@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] RTDM and user space hardware drivers
Date: Mon, 12 Mar 2007 11:33:29 +0000	[thread overview]
Message-ID: <45F53A89.4080409@domain.hid> (raw)
In-Reply-To: <17648569.1173693688643.JavaMail.ngmail@domain.hid>

Hi,

I think you need only a standard kernel driver that mmaps the memory 
area of your pci board.

Thus, from user space program , you mmap it and can do whatever you want 
in userspace world

Best Regards
steph



M. Koehrer wrote:
> Hi everybody,
> 
> the RTDM API is really very good as API for drivers. 
> I have a real time (Xenomai) application in user space that has to access PCI boards.
> The "classical" approach is now to use a kernel driver and to use RTDM as interface
> between the user space application an the kernel space driver.
> However, for performance issues, I prefer to write a pure user mode driver.
> As the memory of the PCI board can be accesses from user space (using /dev/mem) 
> I want to write a pure user space driver  as this seems to me more efficient (and easier to debug) than
> a kernel driver.
> Also, only one application is accessing the driver at a time, I can link the driver directly to my application.
> 
> My questions are now:
> 1. Is it possible to use the RTDM API also for pure user space drivers?
> 
> 2. Is there any experience concerning the performance of a user space driver versus a kernel space
> driver?
> In my use case, I have to write and read about 60 byte (each direction) of (block) data to/from the PCI I/O system.
> 
> Thanks for any ideas or hints on that!
> 
> Regards
> 
> Mathias
> 
> 



  reply	other threads:[~2007-03-12 11:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-12 10:01 [Xenomai-help] RTDM and user space hardware drivers M. Koehrer
2007-03-12 11:33 ` Stéphane ANCELOT [this message]
2007-03-18 10:34 ` 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=45F53A89.4080409@domain.hid \
    --to=sancelot@domain.hid \
    --cc=mathias_koehrer@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.