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
  • samples
  • user_events
  • example.c
Find file BlameHistoryPermalink
  • Beau Belgrave's avatar
    tracing/user_events: Use bits vs bytes for enabled status page data · 39d6d08b
    Beau Belgrave authored Jul 28, 2022
    User processes may require many events and when they do the cache
    performance of a byte index status check is less ideal than a bit index.
    The previous event limit per-page was 4096, the new limit is 32,768.
    
    This change adds a bitwise index to the user_reg struct. Programs check
    that the bit at status_bit has a bit set within the status page(s).
    
    Link: https://lkml.kernel.org/r/20220728233309.1896-6-beaub@linux.microsoft.com
    Link: https://lore.kernel.org/all/2059213643.196683.1648499088753.JavaMail.zimbra@efficios.com/
    
    
    
    Suggested-by: default avatarMathieu Desnoyers <mathieu.desnoyers@efficios.com>
    Signed-off-by: default avatarBeau Belgrave <beaub@linux.microsoft.com>
    Signed-off-by: default avatarSteven Rostedt (Google) <rostedt@goodmis.org>
    39d6d08b
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7