All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] Reworking file descriptors
Date: Sun, 15 Dec 2013 21:58:36 +0100	[thread overview]
Message-ID: <52AE17FC.4070200@xenomai.org> (raw)
In-Reply-To: <52AE0F6D.10007@xenomai.org>

On 12/15/2013 09:22 PM, Gilles Chanteperdrix wrote:
> 
> Hi Jan,
> 
> I have starting reworking the posix skin on forge to use the cobalt
> registry instead of the ad-hoc registry it currently uses. The next step
> for that work is to convert the file descriptors, offering a unified
> access with select to posix skin message queues and rtdm drivers, and
> working correctly with fork().
> 
> I have a clear idea on how I would do it for the posix message queues
> only. Just as I did for the semaphores, I would implement a hash table,
> where the file descriptor structures are indexed by the user-space file
> descriptor (obtained with open(/dev/null) for instance, so that xenomai
> file descriptors follow the posix specification, and use the smallest
> available descriptor), and the mm structure.
> 
> However, RTDM allows opening file descriptors in kernel-space, so it
> would break my implementation, because we can use NULL or &init_mm as
> the mm key, but what would we use as the file descriptor index?

Crazy ideas include calling xnregistry_enter and using the returned
handler as file descriptor in kernel-space, but that would give a
different way to get the file descriptor structure for kernel-space and
user-space.


-- 
                                                                Gilles.


  reply	other threads:[~2013-12-15 20:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-15 20:22 [Xenomai] Reworking file descriptors Gilles Chanteperdrix
2013-12-15 20:58 ` Gilles Chanteperdrix [this message]
2013-12-16 15:07   ` Jan Kiszka
2013-12-16 15:17     ` Gilles Chanteperdrix
2013-12-16 15:29       ` 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=52AE17FC.4070200@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=jan.kiszka@web.de \
    --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.