Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • X xcap-capability-linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • 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
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • xcap
  • xcap-capability-linux
  • Repository

Switch branch/tag
  • xcap-capability-linux
  • fs
  • btrfs
  • transaction.c
Find file BlameHistoryPermalink
  • Alexandru Moise's avatar
    btrfs: trimming some start_transaction() code away · f2f767e7
    Alexandru Moise authored Aug 27, 2015
    
    
    Just call kmem_cache_zalloc() instead of calling kmem_cache_alloc().
    We're just initializing most fields to 0, false and NULL later on
    _anyway_, so to make the code mode readable and potentially gain
    a bit of performance (completely untested claim), we should fill our
    btrfs_trans_handle with zeros on allocation then just initialize
    those five remaining fields (not counting the list_heads) as normal.
    Reviewed-by: default avatarDavid Sterba <dsterba@suse.com>
    Signed-off-by: default avatarAlexandru Moise <00moses.alexander00@gmail.com>
    Signed-off-by: default avatarDavid Sterba <dsterba@suse.com>
    f2f767e7

Replace transaction.c

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.