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
You need to sign in or sign up before continuing.
  • linux
  • kernel
  • workqueue.c
Find file BlameHistoryPermalink
  • Lai Jiangshan's avatar
    workqueue: Remove outdated comment about exceptional workers in unbind_workers() · 11b45b0b
    Lai Jiangshan authored Dec 07, 2021
    Long time before, workers are not ALL bound after CPU_ONLINE, they can
    still be running in other CPUs before self rebinding.
    
    But the commit a9ab775b
    
     ("workqueue: directly restore CPU affinity
    of workers from CPU_ONLINE") makes rebind_workers() bind them all.
    
    So all workers are on the CPU before the CPU is down.
    
    And the comment in unbind_workers() refers to the workers "which are
    still executing works from before the last CPU down" is outdated.
    Just removed it.
    
    Signed-off-by: default avatarLai Jiangshan <laijs@linux.alibaba.com>
    Signed-off-by: default avatarTejun Heo <tj@kernel.org>
    11b45b0b
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7