I think we need to introduce thread mask and at the same time consider the role of cpumask again. My initial thinking is that cpumask could stay in the API, at least ODP API debug type calls and helpers dealing with physical CPU IDs need it. Schedule, etc ODP APIs need thread IDs (worker thread X) instead of physical CPU IDs (physical CPU X). So, this will be handled as part of the larger thread/cpumask API modification – hopefully soon.
-Petri From: lng-odp [mailto:[email protected]] On Behalf Of ext Christophe Milard Sent: Monday, April 20, 2015 8:57 PM To: LNG ODP Mailman List Subject: [lng-odp] cpumask size Hi, I am not sure we came to any conclusion when it comes the getting the size of the CPU mask. There was a proposal from Petri which made sense to me... /** * @return Maximum number of CPUs a mask can hold */ int odp_cpumask_max_cpus(void) But the discussion just died off... Is that OK?
_______________________________________________ lng-odp mailing list [email protected] https://lists.linaro.org/mailman/listinfo/lng-odp
