You are aware that there is no assumption in ODP that the different ODP tasks are threads, right? Gilad
Gilad Ben-Yossef Software Architect EZchip Technologies Ltd. 37 Israel Pollak Ave, Kiryat Gat 82025 ,Israel Tel: +972-4-959-6666 ext. 576, Fax: +972-8-681-1483 Mobile: +972-52-826-0388, US Mobile: +1-973-826-0388 Email: [email protected], Web: http://www.ezchip.com "Ethernet always wins." — Andy Bechtolsheim > -----Original Message----- > From: [email protected] [mailto:lng-odp- > [email protected]] On Behalf Of Shmulik Ladkani > Sent: Monday, November 03, 2014 11:50 AM > To: [email protected] > Subject: [lng-odp] [RFC] Addition to odp_init interface > > Hi, > > I'd like to suggest the following addition to odp_init.h: > > diff --git a/platform/linux-generic/include/api/odp_init.h > b/platform/linux-generic/include/api/odp_init.h > index 8e018cbdba..9b75609fc7 100644 > --- a/platform/linux-generic/include/api/odp_init.h > +++ b/platform/linux-generic/include/api/odp_init.h > @@ -108,6 +108,15 @@ int odp_term_global(void); > */ > int odp_init_local(void); > > +/** > + * Register a function to be called upon thread local initialization > + * > + * XXX: Should the 'init_local_fn' be invoked for currently existing > threads? > + * Probably yes. > + * (Alternative: user must call 'odp_init_local_register' before > the > + * first 'odp_init_local' call) > + */ > +int odp_init_local_register(int (*init_local_fn)(void)); > > Motivation is to allow a custom library built on top of ODP to > initialize its per-thread local data structures. > > Comments? > > Shmulik > > _______________________________________________ > lng-odp mailing list > [email protected] > http://lists.linaro.org/mailman/listinfo/lng-odp _______________________________________________ lng-odp mailing list [email protected] http://lists.linaro.org/mailman/listinfo/lng-odp
