Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • mesa mesa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2,699
    • Issues 2,699
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 910
    • Merge requests 910
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Mesa
  • mesamesa
  • Merge requests
  • !7979

radv: Use VRAM for CS & upload buffer if all VRAM is CPU-visible.

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Bas Nieuwenhuizen requested to merge bnieuwenhuizen/mesa:vram-cs into master Dec 07, 2020
  • Overview 29
  • Commits 3
  • Pipelines 14
  • Changes 9
  • +3% in basemark
  • +1 fps in SotTR (on a base of 46, so ~2% on face value but no clue how rounding works, so could be 0-4%. Both the pre and post numbers are very consistent though, returning exactly the same number for each of 3 runs)

Tested CPU performance with bnieuwenhuizen/vulkan_tests@180c2b67 with no difference found above the noise floor.

Why do this with full VRAM visibility: less CPU-visible VRAM pressure lowers the risk for triggering moving buffers around. Why not do this on APUs: very high VRAM pressure overall

Edited Dec 28, 2020 by Bas Nieuwenhuizen
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: vram-cs