[Xenomai] v3 heap mem-pool-size

[Xenomai] v3 heap mem-pool-size

[Stéphane ANCELOT]

Hi,

Is there a better way to raise mem-pool-size other than specifying in 
cmdline ?

    0"007.389| WARNING: [main] heapobj_init() failed for 470 bytes, 
raise --mem-pool-size?


Regards,
S.Ancelot

Re: [Xenomai] v3 heap mem-pool-size

[Gilles Chanteperdrix]

On Thu, May 07, 2015 at 08:54:31AM +0200, Stéphane ANCELOT wrote:
> Hi,
> 
> Is there a better way to raise mem-pool-size other than specifying in
> cmdline ?
> 
>    0"007.389| WARNING: [main] heapobj_init() failed for 470 bytes, raise
> --mem-pool-size?

A command line option is nice, it allows you to do basically
anything you want by calling your program from a script. What is it
you want to do that can not be achieved this way?

-- 
					    Gilles.

Re: [Xenomai] v3 heap mem-pool-size

[Jeff Webb]

On 05/07/2015 04:07 AM, Gilles Chanteperdrix wrote:
> On Thu, May 07, 2015 at 08:54:31AM +0200, Stéphane ANCELOT wrote:
>> Hi,
>>
>> Is there a better way to raise mem-pool-size other than specifying in
>> cmdline ?
>>
>>     0"007.389| WARNING: [main] heapobj_init() failed for 470 bytes, raise
>> --mem-pool-size?
>
> A command line option is nice, it allows you to do basically
> anything you want by calling your program from a script. What is it
> you want to do that can not be achieved this way?
>

If we don't want to call our application from a script to set appropriate Xenomai parameters, will supplying the --no-auto-init option to xeno-config allow us to set Xenomai run-time options to the desired values by manually calling copperplate_init() from our application?  Are the options that can be passed to copperplate_init() the ones described here [1]?  Do these options apply to applications based on the POSIX skin as well?  If so, I am slightly confused because the documentation (e.g. [2], [3]) that states that all APIs except POSIX are based on the Copperplate library, so it would seem that Copperplate related stuff would not apply to POSIX applications.  I apologize if this is a silly question, but I am still coming up to speed on the new Xenomai 3 architecture.

Thanks,

Jeff

[1] https://xenomai.org/running-applications-with-xenomai-3-x/
[2] http://www.xenomai.org/documentation/xenomai-3/html/man1/xeno-config/index.html
[3] https://xenomai.org/migrating-from-xenomai-2-x-to-3-x/

Re: [Xenomai] v3 heap mem-pool-size

[Stéphane ANCELOT]

On 07/05/2015 11:07, Gilles Chanteperdrix wrote:
> On Thu, May 07, 2015 at 08:54:31AM +0200, Stéphane ANCELOT wrote:
>> Hi,
>>
>> Is there a better way to raise mem-pool-size other than specifying in
>> cmdline ?
>>
>>     0"007.389| WARNING: [main] heapobj_init() failed for 470 bytes, raise
>> --mem-pool-size?
> A command line option is nice, it allows you to do basically
> anything you want by calling your program from a script. What is it
> you want to do that can not be achieved this way?
>
It is a nice idea, however I understand everybody needs are not the same.

Regarding my application, I setup dynamically my heap once. But this 
heap size depends will depend on some external parameters and will vary. 
And the only way to know the size to allocate is to "count" the 
databytes in my C programing structures. Honestly, I am sure a computer
will better do it than my mind.

eg. These external parameters may depend on how many motors in my 
machine, and so on.

Regards,
S.Ancelot

Re: [Xenomai] v3 heap mem-pool-size

[Gilles Chanteperdrix]

On Thu, May 07, 2015 at 03:44:29PM +0200, Stéphane ANCELOT wrote:
> On 07/05/2015 11:07, Gilles Chanteperdrix wrote:
> >On Thu, May 07, 2015 at 08:54:31AM +0200, Stéphane ANCELOT wrote:
> >>Hi,
> >>
> >>Is there a better way to raise mem-pool-size other than specifying in
> >>cmdline ?
> >>
> >>    0"007.389| WARNING: [main] heapobj_init() failed for 470 bytes, raise
> >>--mem-pool-size?
> >A command line option is nice, it allows you to do basically
> >anything you want by calling your program from a script. What is it
> >you want to do that can not be achieved this way?
> >
> It is a nice idea, however I understand everybody needs are not the same.

You asked for a "better way", I just tried and guessed what it
means, despite the fact that it was yet another unjustified critic
of Xenomai. Maybe if the question had been precise like "is there a way
to programmaticaly set "mem-pool-size", would you have get an answer
to your question.

-- 
					    Gilles.

Re: [Xenomai] v3 heap mem-pool-size

[Stéphane ANCELOT]

On 07/05/2015 17:32, Gilles Chanteperdrix wrote:
> On Thu, May 07, 2015 at 03:44:29PM +0200, Stéphane ANCELOT wrote:
>> On 07/05/2015 11:07, Gilles Chanteperdrix wrote:
>>> On Thu, May 07, 2015 at 08:54:31AM +0200, Stéphane ANCELOT wrote:
>>>> Hi,
>>>>
>>>> Is there a better way to raise mem-pool-size other than specifying in
>>>> cmdline ?
>>>>
>>>>     0"007.389| WARNING: [main] heapobj_init() failed for 470 bytes, raise
>>>> --mem-pool-size?
>>> A command line option is nice, it allows you to do basically
>>> anything you want by calling your program from a script. What is it
>>> you want to do that can not be achieved this way?
>>>
>> It is a nice idea, however I understand everybody needs are not the same.
> You asked for a "better way", I just tried and guessed what it
> means, despite the fact that it was yet another unjustified critic
> of Xenomai. Maybe if the question had been precise like "is there a way
> to programmaticaly set "mem-pool-size", would you have get an answer
> to your question.
>
Hi,

In reply to the latest question :

"""What is it you want to do that can not be achieved this way? """

My last complete answer was :

"""
  It is a nice idea, however I understand everybody needs are not the same.

Regarding my application, I setup dynamically my heap once. But this 
heap size depends will depend on some external parameters and will vary. 
And the only way to know the size to allocate is to "count" the 
databytes in my C programing structures. Honestly, I am sure a computer 
will better do it than my mind.

eg. These external parameters may depend on how many motors in my 
machine, and so on.

"""

It bothers megetting these kinds of personal judgement in reply, 
furthermore out of topic and in a wrong context. Furthermore a waste of 
time.

I would suggest a bit of sagacity on both sides, as I do, e.g. trying to 
understand :
why we need to round up small heap sizes to at least 2048 bytes ?
why heaps are not allocated if I setup 0 size in rt_heap_alloc() ?
why I have to  setup mem-pool-size in xenomai v3 ?
and so on ....

I am pretty sure that there are good reasons , in some contexts. 
Unfortunately, not in my context, may be not in bob's or alice's context 
too....
Precisely, my last question was asking if either I need to make a 
program for computing estimate heap space needed and set it in cmdline,
or if there is a workaround to programmatically set cmdline 
mem-pool-size option?
And in the first case, I think there is unfortunately  some regression .

Regards,
Steph.

Re: [Xenomai] v3 heap mem-pool-size

[Philippe Gerum]

On 05/07/2015 03:14 PM, Jeff Webb wrote:
> On 05/07/2015 04:07 AM, Gilles Chanteperdrix wrote:
>> On Thu, May 07, 2015 at 08:54:31AM +0200, Stéphane ANCELOT wrote:
>>> Hi,
>>>
>>> Is there a better way to raise mem-pool-size other than specifying in
>>> cmdline ?
>>>
>>>     0"007.389| WARNING: [main] heapobj_init() failed for 470 bytes,
>>> raise
>>> --mem-pool-size?
>>
>> A command line option is nice, it allows you to do basically
>> anything you want by calling your program from a script. What is it
>> you want to do that can not be achieved this way?
>>
> 
> If we don't want to call our application from a script to set
> appropriate Xenomai parameters, will supplying the --no-auto-init option
> to xeno-config allow us to set Xenomai run-time options to the desired
> values by manually calling copperplate_init() from our application?  Are
> the options that can be passed to copperplate_init() the ones described
> here [1]?  Do these options apply to applications based on the POSIX
> skin as well?  If so, I am slightly confused because the documentation
> (e.g. [2], [3]) that states that all APIs except POSIX are based on the
> Copperplate library, so it would seem that Copperplate related stuff
> would not apply to POSIX applications.  I apologize if this is a silly
> question, but I am still coming up to speed on the new Xenomai 3
> architecture.
> 

No silly question for sure. These questions definitely illustrate
usability issues with respect to the init sequence which I'm working on.
I'll follow up on this asap.

-- 
Philippe.

Re: [Xenomai] v3 heap mem-pool-size

[Stéphane ANCELOT]

On 11/05/2015 16:14, Philippe Gerum wrote:
> On 05/07/2015 03:14 PM, Jeff Webb wrote:
>> On 05/07/2015 04:07 AM, Gilles Chanteperdrix wrote:
>>> On Thu, May 07, 2015 at 08:54:31AM +0200, Stéphane ANCELOT wrote:
>>>> Hi,
>>>>
>>>> Is there a better way to raise mem-pool-size other than specifying in
>>>> cmdline ?
>>>>
>>>>      0"007.389| WARNING: [main] heapobj_init() failed for 470 bytes,
>>>> raise
>>>> --mem-pool-size?
>>> A command line option is nice, it allows you to do basically
>>> anything you want by calling your program from a script. What is it
>>> you want to do that can not be achieved this way?
>>>
>> If we don't want to call our application from a script to set
>> appropriate Xenomai parameters, will supplying the --no-auto-init option
>> to xeno-config allow us to set Xenomai run-time options to the desired
>> values by manually calling copperplate_init() from our application?  Are
>> the options that can be passed to copperplate_init() the ones described
>> here [1]?  Do these options apply to applications based on the POSIX
>> skin as well?  If so, I am slightly confused because the documentation
>> (e.g. [2], [3]) that states that all APIs except POSIX are based on the
>> Copperplate library, so it would seem that Copperplate related stuff
>> would not apply to POSIX applications.  I apologize if this is a silly
>> question, but I am still coming up to speed on the new Xenomai 3
>> architecture.
>>
> No silly question for sure. These questions definitely illustrate
> usability issues with respect to the init sequence which I'm working on.
> I'll follow up on this asap.
>
Thanks

Re: [Xenomai] v3 heap mem-pool-size

[Jeff Webb]

On 05/11/2015 09:14 AM, Philippe Gerum wrote:
> On 05/07/2015 03:14 PM, Jeff Webb wrote:
>> On 05/07/2015 04:07 AM, Gilles Chanteperdrix wrote:
>>> On Thu, May 07, 2015 at 08:54:31AM +0200, Stéphane ANCELOT wrote:
>>>> Hi,
>>>>
>>>> Is there a better way to raise mem-pool-size other than specifying in
>>>> cmdline ?
>>>>
>>>>      0"007.389| WARNING: [main] heapobj_init() failed for 470 bytes,
>>>> raise
>>>> --mem-pool-size?
>>>
>>> A command line option is nice, it allows you to do basically
>>> anything you want by calling your program from a script. What is it
>>> you want to do that can not be achieved this way?
>>>
>>
>> If we don't want to call our application from a script to set
>> appropriate Xenomai parameters, will supplying the --no-auto-init option
>> to xeno-config allow us to set Xenomai run-time options to the desired
>> values by manually calling copperplate_init() from our application?  Are
>> the options that can be passed to copperplate_init() the ones described
>> here [1]?  Do these options apply to applications based on the POSIX
>> skin as well?  If so, I am slightly confused because the documentation
>> (e.g. [2], [3]) that states that all APIs except POSIX are based on the
>> Copperplate library, so it would seem that Copperplate related stuff
>> would not apply to POSIX applications.  I apologize if this is a silly
>> question, but I am still coming up to speed on the new Xenomai 3
>> architecture.
>>
>
> No silly question for sure. These questions definitely illustrate
> usability issues with respect to the init sequence which I'm working on.
> I'll follow up on this asap.
>

Thanks, Philippe.

-Jeff

Re: [Xenomai] v3 heap mem-pool-size

[Philippe Gerum]

On 05/07/2015 03:14 PM, Jeff Webb wrote:
> On 05/07/2015 04:07 AM, Gilles Chanteperdrix wrote:
>> On Thu, May 07, 2015 at 08:54:31AM +0200, Stéphane ANCELOT wrote:
>>> Hi,
>>>
>>> Is there a better way to raise mem-pool-size other than specifying in
>>> cmdline ?
>>>
>>>     0"007.389| WARNING: [main] heapobj_init() failed for 470 bytes,
>>> raise
>>> --mem-pool-size?
>>
>> A command line option is nice, it allows you to do basically
>> anything you want by calling your program from a script. What is it
>> you want to do that can not be achieved this way?
>>
> 
> If we don't want to call our application from a script to set
> appropriate Xenomai parameters, will supplying the --no-auto-init option
> to xeno-config allow us to set Xenomai run-time options to the desired
> values by manually calling copperplate_init() from our application?  Are
> the options that can be passed to copperplate_init() the ones described
> here [1]?  Do these options apply to applications based on the POSIX
> skin as well?  If so, I am slightly confused because the documentation
> (e.g. [2], [3]) that states that all APIs except POSIX are based on the
> Copperplate library, so it would seem that Copperplate related stuff
> would not apply to POSIX applications.  I apologize if this is a silly
> question, but I am still coming up to speed on the new Xenomai 3
> architecture.
> 

There used to be an inconsistency regarding this, because POSIX apps did
not share the same init sequence internally than non-POSIX ones. This
has been fixed by recent changes, available from the master branch.
The new (common) init sequence of all Xenomai applications is described
in this document: http://xenomai.org/2015/05/application-setup-and-init/

You may be interested in using the tunables:
http://xenomai.org/2015/05/application-setup-and-init/#Configuration_and_runtime_tunables

I have checked this approach with a large, real world application, which
looks good so far. Please let me know if that addresses your
requirements as well. Thanks,

-- 
Philippe.

Re: [Xenomai] v3 heap mem-pool-size

[Stéphane ANCELOT]

On 24/05/2015 10:29, Philippe Gerum wrote:
> On 05/07/2015 03:14 PM, Jeff Webb wrote:
>> On 05/07/2015 04:07 AM, Gilles Chanteperdrix wrote:
>>> On Thu, May 07, 2015 at 08:54:31AM +0200, Stéphane ANCELOT wrote:
>>>> Hi,
>>>>
>>>> Is there a better way to raise mem-pool-size other than specifying in
>>>> cmdline ?
>>>>
>>>>      0"007.389| WARNING: [main] heapobj_init() failed for 470 bytes,
>>>> raise
>>>> --mem-pool-size?
>>> A command line option is nice, it allows you to do basically
>>> anything you want by calling your program from a script. What is it
>>> you want to do that can not be achieved this way?
>>>
>> If we don't want to call our application from a script to set
>> appropriate Xenomai parameters, will supplying the --no-auto-init option
>> to xeno-config allow us to set Xenomai run-time options to the desired
>> values by manually calling copperplate_init() from our application?  Are
>> the options that can be passed to copperplate_init() the ones described
>> here [1]?  Do these options apply to applications based on the POSIX
>> skin as well?  If so, I am slightly confused because the documentation
>> (e.g. [2], [3]) that states that all APIs except POSIX are based on the
>> Copperplate library, so it would seem that Copperplate related stuff
>> would not apply to POSIX applications.  I apologize if this is a silly
>> question, but I am still coming up to speed on the new Xenomai 3
>> architecture.
>>
> There used to be an inconsistency regarding this, because POSIX apps did
> not share the same init sequence internally than non-POSIX ones. This
> has been fixed by recent changes, available from the master branch.
> The new (common) init sequence of all Xenomai applications is described
> in this document: http://xenomai.org/2015/05/application-setup-and-init/
>
> You may be interested in using the tunables:
> http://xenomai.org/2015/05/application-setup-and-init/#Configuration_and_runtime_tunables
>
> I have checked this approach with a large, real world application, which
> looks good so far. Please let me know if that addresses your
> requirements as well. Thanks,

Hi,
So, if I understand, if I want two programs using shared heaps area, I
have to define session setting ?
Regards,
Steph

Re: [Xenomai] v3 heap mem-pool-size

[Stéphane ANCELOT]

Hi,

I tried git version.

I am able to create heaps in one program. No problem.
but altough, I enabled pshared, I can not bind on these heaps from 
another program.

rt_heap_bind fails with "Resource temporary unavailable."

Regards,
S.Ancelot


On 24/05/2015 10:29, Philippe Gerum wrote:
> On 05/07/2015 03:14 PM, Jeff Webb wrote:
>> On 05/07/2015 04:07 AM, Gilles Chanteperdrix wrote:
>>> On Thu, May 07, 2015 at 08:54:31AM +0200, Stéphane ANCELOT wrote:
>>>> Hi,
>>>>
>>>> Is there a better way to raise mem-pool-size other than specifying in
>>>> cmdline ?
>>>>
>>>>      0"007.389| WARNING: [main] heapobj_init() failed for 470 bytes,
>>>> raise
>>>> --mem-pool-size?
>>> A command line option is nice, it allows you to do basically
>>> anything you want by calling your program from a script. What is it
>>> you want to do that can not be achieved this way?
>>>
>> If we don't want to call our application from a script to set
>> appropriate Xenomai parameters, will supplying the --no-auto-init option
>> to xeno-config allow us to set Xenomai run-time options to the desired
>> values by manually calling copperplate_init() from our application?  Are
>> the options that can be passed to copperplate_init() the ones described
>> here [1]?  Do these options apply to applications based on the POSIX
>> skin as well?  If so, I am slightly confused because the documentation
>> (e.g. [2], [3]) that states that all APIs except POSIX are based on the
>> Copperplate library, so it would seem that Copperplate related stuff
>> would not apply to POSIX applications.  I apologize if this is a silly
>> question, but I am still coming up to speed on the new Xenomai 3
>> architecture.
>>
> There used to be an inconsistency regarding this, because POSIX apps did
> not share the same init sequence internally than non-POSIX ones. This
> has been fixed by recent changes, available from the master branch.
> The new (common) init sequence of all Xenomai applications is described
> in this document: http://xenomai.org/2015/05/application-setup-and-init/
>
> You may be interested in using the tunables:
> http://xenomai.org/2015/05/application-setup-and-init/#Configuration_and_runtime_tunables
>
> I have checked this approach with a large, real world application, which
> looks good so far. Please let me know if that addresses your
> requirements as well. Thanks,
>