All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Andreas Glatz <AndreasGlatz@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] rt_queue_create in RT task?
Date: Mon, 09 Mar 2009 17:08:04 +0100	[thread overview]
Message-ID: <49B53EE4.1030008@domain.hid> (raw)
In-Reply-To: <1236608449.3587.32.camel@domain.hid>

Andreas Glatz wrote:
> Hi,
> 
> Calling rt_queue_create in a real-time task is supposed to fail
> according to the documentation. 
>

It fails from kernel space, otherwise, from user-space, your application would 
simply be moved to a Linux context automatically for processing the 
rt_queue_create() syscall.

> I found out, that the reason for this is, that the memory for 
> the queue memory pool is allocated with vmalloc/kmalloc. 
> Is there another reason?
> 

No, that's the main reason, along with other Linux memory management ops to map 
the pool to user-space if Q_SHARED is passed.

> I still would like to be able to call rt_queue_create in a 
> real-time task in my activity of porting real-time applications
> to Xenomai because I think that patching rt_queue_create would
> be less time consuming than redesigning the applications.
> 

You mean that it would be faster to hack rt_queue_create() than moving your 
real-time code to userland? Well, probably, fair enough. However, you will 
probably lose much more time debugging your port from kernel space than it would 
have cost you to move it to user-space and benefit from the GDB support there. YMMV.

> My approach to get there would be to split rt_queue_create into 
> two separate functions, one that allocates the memory pool
> and another one which initializes the queue structure... 
>

Then don't work at RT_HEAP level, but rather manipulate the internal xnheap 
object from the RT_QUEUE descriptor instead (bufpool). You would basically have 
to change the bufpool field to become a pointer to the actual heap object, and 
keep the rest unchanged.

> Best regards,
> Andreas
> 
> 
>  
> 
> _______________________________________________
> Xenomai-core mailing list
> Xenomai-core@domain.hid
> https://mail.gna.org/listinfo/xenomai-core
> 


-- 
Philippe.


  parent reply	other threads:[~2009-03-09 16:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-09 14:20 [Xenomai-core] rt_queue_create in RT task? Andreas Glatz
2009-03-09 14:36 ` Steven Seeger
2009-03-09 15:19   ` Andreas Glatz
2009-03-09 15:32     ` Steven Seeger
2009-03-09 16:08 ` Philippe Gerum [this message]
2009-03-09 16:37   ` Andreas Glatz
2009-03-09 17:02     ` Philippe Gerum
2009-03-10 12:43       ` Andreas Glatz

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=49B53EE4.1030008@domain.hid \
    --to=rpm@xenomai.org \
    --cc=AndreasGlatz@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.