On Feb 14, 2011, at 8:23 AM, Samuel Thibault wrote: >> Let's not use "cpu" -- how about get_current_cpubind? (vs. get_cpubind) > > The point is precisely that it's not the cpu binding, but where the > thread is actually _running_ precisely.
Hmm; ok. I like the word "current" in here, somehow. Gives the connotation that it might change in the future (if it's not bound). Maybe get_current_cpuset? -- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
