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
  • Zqiang's avatar
    workqueue: Use the kmem_cache_free() instead of kfree() to release pwq · 7b42f401
    Zqiang authored Oct 11, 2023
    
    
    Currently, the kfree() be used for pwq objects allocated with
    kmem_cache_alloc() in alloc_and_link_pwqs(), this isn't wrong.
    but usually, use "trace_kmem_cache_alloc/trace_kmem_cache_free"
    to track memory allocation and free. this commit therefore use
    kmem_cache_free() instead of kfree() in alloc_and_link_pwqs()
    and also consistent with release of the pwq in rcu_free_pwq().
    
    Signed-off-by: default avatarZqiang <qiang.zhang1211@gmail.com>
    Signed-off-by: default avatarTejun Heo <tj@kernel.org>
    7b42f401
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7