> Conti..
>
> Root cause of my concern is not entirely specific to this patch. Its
> more related to odp api initialization calling sequence in
> application. From early days, we used to follow below step in
> application -
>
> odp_global_init() -> which does almost everything for platform
> initialization.
> odp_shm_reserve() -> used for argument processing then
> odp_create_thread etc...
>
> Now we found a need to introduce platform specific init hints, coming
> from application. Therefore order of odp_xxx_init api calling sequence
> should change too.
>
>
> Something like.
>
> Application "X"
>
> main ()
> {
>
> - First do argument processing. For that, call odp_shm_init() in
> application and remove it from odp_global_init OR application has to
> allocate memory(bad idea ... I guess).
argX and argY can be allocated from stack or heap (malloc). Shared memory is
not needed for those to be able to call odp_global_init(). ODP will take copy
of the argument, argX/Y can be destroyed after the call.
After ODP init, you can allocate shm and copy args there if you need to share
those within your app.
-Petri
>
> - Then call odp_global/platform_init(argX, argY); where arg -X :
> global param, Y : platform centric stuff.
>
> ... Rest stuff as it is.
> }
>
>
> Any idea? thoughts? Does above make sense. Thanks.
>
>
_______________________________________________
lng-odp mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/lng-odp
