RPC and RTEMS task variables

[Joel Sherrill]

On Mon, Feb 29, 2016 at 5:44 PM, Aun-Ali Zaidi <admin at kodeit.net> wrote:

> $ grep -lR "task_var"
> .git/objects/pack/pack-97a9b54f14bf9a5b8987276468b6bf120d1f2ab4.pack
> c/src/lib/libbsp/powerpc/mvme5500/vectors/exceptionhandler.c
> c/src/lib/libbsp/powerpc/gen5200/include/bestcomm.h
> c/src/ada/rtems-tasks.adb
> cpukit/librpc/src/rpc/svc.c
> cpukit/librpc/src/rpc/rtems_rpc.c
> cpukit/librpc/src/rpc/svc_raw.c
> cpukit/librpc/src/rpc/clnt_simple.c
> cpukit/librpc/src/rpc/clnt_perror.c
> cpukit/librpc/src/rpc/svc_simple.c
> cpukit/librpc/src/rpc/svc_auth.c
> cpukit/librpc/src/rpc/rpcdname.c
> cpukit/librpc/include/rpc/rpc.h
> cpukit/rtems/include/rtems/rtems/tasks.h
> doc/user/smp.t
> doc/user/task.t
>
>
>
Obviously used the wrong grep. :)

I would recommend pthread_key's. They are simple and work on all targets.

--joel


> On 02/29/2016 05:34 PM, Joel Sherrill wrote:
>
>
>
> On Mon, Feb 29, 2016 at 4:56 PM, Aun-Ali Zaidi <admin at kodeit.net> wrote:
>
>> Greetings,
>>
>> I am currently removing the deprecated task variables and am having
>> issues deciding on what to do with the use
>> of task variables in the RPC implementation. The next email will include
>> a patch of my current tested and working progress.
>>
>>
> Where do you see them used? I don't see them used in the current tree.
>
> $ grep -rl rtems_task_variable_add .
> ./cpukit/rtems/src/taskvariableadd.c
> ./cpukit/rtems/include/rtems/rtems/tasks.h
> ./cpukit/rtems/mainpage.h
> ./doc/user/task.t
> ./c/src/lib/libbsp/powerpc/mvme5500/vectors/exceptionhandler.c
> ./c/src/ada/rtems-tasks.adb
> ./testsuites/psxtests/psxconfig01/init.c
> ./testsuites/sptests/sp28/init.c
>
>
>
>> Any suggestions?
>>
>> Thanks,
>> Aun-Ali Zaidi
>>
>> _______________________________________________
>> devel mailing list
>> devel at rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20160229/170f38aa/attachment-0002.html>