All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] Enhanced RTDM device closure
Date: Wed, 21 Feb 2007 09:43:15 +0100	[thread overview]
Message-ID: <45DC0623.3080706@domain.hid> (raw)

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

Hi,

a few changes of the RTDM layer were committed to trunk recently. They
make handling of RTDM file descriptors more handy:

 o rt_dev_close/POSIX-close now polls as long as the underlying device
   reports -EAGAIN. No more looping inside the application is required.
   This applies to the usual non-RT invocation of close, the corner
   case "close from RT context" can still return EAGAIN.

 o Automatic cleanup of open file descriptors has been implemented. This
   is not yet the perfect design (*), but a straightforward approach to
   ease the cleanup after application crashes or other unexpected
   terminations.

The code is still young, so testers are welcome.

Jan


(*) Actually, I would like to see generic per-process file descriptor
tables one day, used by both the POSIX and the RTDM skin. The FD table
should be obtained via xnshadow_ppd_get(). But first this requires
lock-less xnshadow_ppd_get() based on ipipe_get_ptd() to keep the
overhead limited. Yet another story.


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

             reply	other threads:[~2007-02-21  8:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-21  8:43 Jan Kiszka [this message]
2007-02-21  8:56 ` [Xenomai-core] Enhanced RTDM device closure Gilles Chanteperdrix
2007-02-21  9:11   ` Jan Kiszka
2007-02-21  9:40     ` Gilles Chanteperdrix
2007-02-21  9:57       ` Jan Kiszka
2007-02-21 10:29         ` Gilles Chanteperdrix
2007-02-21 10:48           ` Jan Kiszka
2007-02-25 15:36 ` 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=45DC0623.3080706@domain.hid \
    --to=jan.kiszka@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.