Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • N nrm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • argo
  • nrm
  • Issues
  • #20
Closed
Open
Issue created Nov 29, 2018 by Sridutt Bhalachandra@sriduttbContributor3 of 3 checklist items completed3/3 checklist items

Support for Process/Task pinning

Need NRM to support Process/Task pinning to a core. This is important for allowing the use of power policies that use contextual information from an application phase and use it for computing frequency levels for the next phase. In absence of process/task pinning, the contextual information obtained does not serve any value as it is not representative of application phase behavior on a core as the processes and task can migrate during the next phase.

For NRM to support process/task pinning within a container we need to

  • Add appropriate options in the manifest file
  • Compute the correct bitmask in the ContainerManager
  • Use the computed bitmask in "hwloc-bind" to launch each process in the conatiner by prepending it as an argument to the command line e.g. as does in the case of "perf" (ContainerManager)
Edited Jan 10, 2019 by Sridutt Bhalachandra
Assignee
Assign to
Time tracking