From: Makarand Pradhan <makarandpradhan@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] realtime pipes
Date: Mon, 16 Jan 2012 10:36:10 -0500 [thread overview]
Message-ID: <4F1443EA.6050906@domain.hid> (raw)
In-Reply-To: <4F144123.9050904@domain.hid>
Thanks.
On 16/01/12 10:24 AM, Philippe Gerum wrote:
> On 01/16/2012 04:09 PM, Makarand Pradhan wrote:
>> Thanks Philippe.
>>
>> To ensure that I understand correctly, let me rephrase my understanding.
>>
>> In 3.0, the rt_pipe_create and friends will cease to exist. We have to
>> start using the sockets with domain AF_RTIPC and protocol IPCPROTO_XDDP
>> instead.
>>
>> Is that a correct statement?
> Basically, yes. In addition, X3 will keep the RT_PIPE interface for the
> -rt endpoint available on the application-side, by wrapping a XDDP
> socket to a RT_PIPE descriptor under the hood. In kernel space however,
> the RT_PIPE API to create -rt endpoints won't be available anymore, one
> will have to create them via the rtdm_socket/rt_dev_socket calls.
>
> In any case, the API for the non-rt side does not change, i.e. POSIX
> file I/O calls will still be the way to interface with the -rt endpoint.
>
>> Rgds,
>> Mak.
>>
>> On 16/01/12 09:35 AM, Philippe Gerum wrote:
>>> On 01/16/2012 03:25 PM, Makarand Pradhan wrote:
>>>> Hi,
>>>>
>>>> "Real-time pipes are deprecated."
>>>>
>>>> We use a lot of rt pipes. So, can you pl elaborate on this? I would
>>>> highly appreciate if you can comment on the following.
>>>>
>>>> 1. When will the rt pipe interface be removed? Any time frame?
>>> Xenomai 3. Xenomai 2.x will keep them forever.
>>>
>>>> 2. Would like to understand the reason for deprecating the interface.
>>>>
>>> - Because there is a better socket-based API implemented by the RTIPC
>>> driver w/ the XDDP protocol, which does not require running application
>>> level code in kernel space (RT_PIPE is definitely an application level
>>> API). This new interface is available since Xenomai 2.5.x. It is
>>> functionally 100% equivalent to the legacy RT_PIPE API.
>>>
>>> - Because no support will be provided in Xenomai 3 for running
>>> application level code in kernel space, so RT_PIPE have to go from
>>> kernel space. However, RT_PIPE are still part of the user-space API of
>>> Xenomai 3, interfacing with XDDP endpoints in kernel space.
>>>
>>> I'm really referring to application level code, by contrast to RTDM
>>> driver level code which will obviously remain a first-class citizen in
>>> kernel space.
>>>
>>> See:
>>>
>>> o http://www.xenomai.org/index.php/Xenomai:Roadmap
>>>
>>> o
>>> http://www.xenomai.org/documentation/xenomai-2.6/html/api/group__rtipc.html
>>>
>>>
>>> o examples/rtdm/profiles/ipc in the Xenomai distro
>>>
>>>> Thanks and Rgds,
>>>> Mak.
>>>>
>>>>
>>>> On 15/01/12 12:37 PM, Gilles Chanteperdrix wrote:
>>>>> Real-time pipes are deprecated.
>>
>
--
___________________________________________________________________________
NOTICE OF CONFIDENTIALITY:
This e-mail and any attachments may contain confidential and privileged information. If you are
not the intended recipient, please notify the sender immediately by return e-mail and delete this
e-mail and any copies. Any dissemination or use of this information by a person other than the
intended recipient is unauthorized and may be illegal.
_____________________________________________________________________
prev parent reply other threads:[~2012-01-16 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 12:36 [Xenomai-core] realtime pipes Jan-Erik Lange
2012-01-15 17:37 ` Gilles Chanteperdrix
[not found] ` <BLU166-W8A6F8615612DBB382F22FC4820@domain.hid>
2012-01-15 18:55 ` [Xenomai-core] FW: " Jan-Erik Lange
2012-01-16 14:25 ` [Xenomai-core] " Makarand Pradhan
2012-01-16 14:35 ` Philippe Gerum
2012-01-16 15:09 ` Makarand Pradhan
2012-01-16 15:24 ` Philippe Gerum
2012-01-16 15:36 ` Makarand Pradhan [this message]
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=4F1443EA.6050906@domain.hid \
--to=makarandpradhan@domain.hid \
--cc=rpm@xenomai.org \
--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.