Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • K kvmtool-dm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • linux-arm
  • kvmtool-dm
  • Repository
  • kvmtool-dm
  • include
  • kvm
  • virtio.h
Find file BlameHistoryPermalink
  • Asias He's avatar
    kvm tools: Improve virtio blk request processing · 2fddfdb5
    Asias He authored Nov 28, 2011
    
    
    There are at most bdev->reqs[VIRTIO_BLK_QUEUE_SIZE] outstanding requests
    at any time.  We can simply use the head of each request to fetch the
    right 'struct blk_dev_req' in bdev->reqs[].
    
    So, we can eliminate the list and lock operations which introduced by
    virtio_blk_req_{pop, push}.
    
    Signed-off-by: default avatarAsias He <asias.hejun@gmail.com>
    Signed-off-by: default avatarPekka Enberg <penberg@kernel.org>
    2fddfdb5