Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • L linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • linux
  • Repository
  • linux
  • kernel
  • workqueue.c
Find file BlameHistoryPermalink
  • Mike Galbraith's avatar
    workqueue: schedule WORK_CPU_UNBOUND work on wq_unbound_cpumask CPUs · ef557180
    Mike Galbraith authored Feb 09, 2016
    
    
    WORK_CPU_UNBOUND work items queued to a bound workqueue always run
    locally.  This is a good thing normally, but not when the user has
    asked us to keep unbound work away from certain CPUs.  Round robin
    these to wq_unbound_cpumask CPUs instead, as perturbation avoidance
    trumps performance.
    
    tj: Cosmetic and comment changes.  WARN_ON_ONCE() dropped from empty
        (wq_unbound_cpumask AND cpu_online_mask).  If we want that, it
        should be done when config changes.
    
    Signed-off-by: default avatarMike Galbraith <umgwanakikbuti@gmail.com>
    Signed-off-by: default avatarTejun Heo <tj@kernel.org>
    ef557180
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7