Charles, The software ensures the core - numa (memory controller) pairing is on the same package. That said, if circumstances dictate that the algorithm has to pick a core paired to a different numa domain, then the task will be permitted to interact with two numa domains. This is a tetris problem - the scheduling algorithm is implemented to minimize these types of situations.
Chris On Thu, Dec 15, 2016 at 2:38 PM, Charles Allen < [email protected]> wrote: > Super cool! does this also support limiting which memory controller the > tasks can use? > > On Thu, Dec 15, 2016 at 10:00 AM Zhitao Li <[email protected]> wrote: > >> Thanks for sharing. This is very interesting to us because we are also >> looking for solution for latency sensitive CPU isolation. >> >> On Thu, Dec 15, 2016 at 9:56 AM, ct clmsn <[email protected]> wrote: >> >> I'll add in BUILD instructions tonight/this weekend. I'll be releasing >> some performance counter tools to use in a mesos system (for container >> applications) very soon. >> >> On Thu, Dec 15, 2016 at 12:13 PM, tommy xiao <[email protected]> wrote: >> >> thanks for your sharing. v5 >> >> 2016-12-15 23:40 GMT+08:00 ct clmsn <[email protected]>: >> >> I've completed a mesos module to support cgroups cpusets. This work is >> related to a JIRA ticket that I posted last spring (MESOS-5342). Apologies >> for the long delay wrapping up the implementation. >> >> https://github.com/ct-clmsn/mesos-cpusets >> >> If you test it out, have issues, or want to make improvements, please >> post to github - I've done some very simple/trivial testing. >> >> Chris >> >> >> >> >> -- >> Deshi Xiao >> Twitter: xds2000 >> E-mail: xiaods(AT)gmail.com >> >> >> >> >> >> -- >> Cheers, >> >> Zhitao Li >> >
