Thread binding

[abouteiller]

Original report by George Bosilca (Bitbucket: bosilca, GitHub: bosilca).

---

As of today only the communication thread can be bound on a set of cores, all other PaRSEC threads must be bound to a single core using the core logical id. However, in a mixed model, PaRSEC + OpenMP, we might want to allow a PaRSEC thread to span across multiple cores, so that the OpenMP team can inherit it's bindings. Moreover, to support the OpenMP + PaRSEC model, we would need to allow the master of each OpenMP teams to call a PaRSEC function to jump right in the PaRSEC execution. In such a case we should avoid the thread binding (so we will need to split the pthread start function in 2 stages, binding and execution).