[PATCH] confdefs: Add declaration for unlimited objects.

[Joel Sherrill]

On 03/26/2012 04:52 PM, Gedare Bloom wrote:
> If any intrepid potential GSOC students want to take a crack at
> writing a patch this could be a good opportunity! :)
>
> /me doesn't want to write doc right now ;)
Your first email was all but the documentation.

It looks like Unlimited Objects should get its own
subsection heading now. The documentation should
mention that configuring with unified workspace
is highly recommended when using unlimited
objects.

--joel
> -Gedare
>
> On Mon, Mar 26, 2012 at 5:38 PM, Joel Sherrill
> <joel.sherrill at oarcorp.com>  wrote:
>> On 03/26/2012 04:31 PM, Gedare Bloom wrote:
>>> Messed up :) This description should have preceded the patch. Oh well.
>>>
>>> I wrote this because of a request in IRC (By Peer) asking whether a
>>> similar mechanism existed.
>> I think this is a handy option. If you will add some documentation
>> to doc/user/conf.t, then it is OK to apply.
>>> -Gedare
>>>
>>> On Mon, Mar 26, 2012 at 5:28 PM, Gedare Bloom<gedare at rtems.org>    wrote:
>>>> This patch adds a macro to ease writing a configuration when the user
>>>> does not care about resource limits / determinism. Such a case arises
>>>> frequently when porting software to RTEMS when the precise resource
>>>> requirements of the software is unknown. By allowing users to declare
>>>> all resources as being unlimited the user will be able to easily avoid
>>>> having to identify which resources are included and define the resource
>>>> limits.
>>>>
>>>> I tested this patch only with the unlimited sample, which uses unlimited
>>>> tasks. The other classic resources and posix resources have not been
>>>> tested
>>>> to verify that they will work properly when using unlimited objects. Due
>>>> to how the posix objects' memory requirements are configured in confdefs
>>>> this patch does not provide unlimited declarations for posix keys or
>>>> queued signals.
>>>>
>>>> If a user provides a value for a configured number of resources that
>>>> value will be used instead of the unlimited. If a user does not specify
>>>> an allocation size the default size of 8 objects is used. This macro does
>>>> not
>>>> support varying the allocation sizes for different objects; users who
>>>> want that
>>>> much control can define the unlimited macros themselves.
>>> _______________________________________________
>>> rtems-devel mailing list
>>> rtems-devel at rtems.org
>>> http://www.rtems.org/mailman/listinfo/rtems-devel
>>
>>
>> --
>> Joel Sherrill, Ph.D.             Director of Research&     Development
>> joel.sherrill at OARcorp.com        On-Line Applications Research
>> Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>>     Support Available             (256) 722-9985
>>
>>
>> _______________________________________________
>> rtems-devel mailing list
>> rtems-devel at rtems.org
>> http://www.rtems.org/mailman/listinfo/rtems-devel


-- 
Joel Sherrill, Ph.D.             Director of Research&   Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
     Support Available             (256) 722-9985