Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
mesa
mesa
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2,362
    • Issues 2,362
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 664
    • Merge Requests 664
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Mesa
  • mesamesa
  • Issues
  • #25

Closed
Open
Opened Jun 25, 2019 by Rob Clark@robclark💬Owner

memory optimizations

we currently keep a number of bo's per-ctx rather than per-screen:

  • blit_mem
  • vsc_data/vsc_data2

However these are (at least currently) only used within the context of a batch, ie. values don't matter across batches. We could save some memory in cases where there are many contexts by moving these to the screen.

However, if we do ever decide to enable intra-batch/submit context switches, we probably want to have these buffers per-priority level (so different contexts hanging off same screen, but with different priority levels, don't stomp on each other). Probably the thing to do is have some static-inline fd6_context_foo_mem() accessors which grab the bo from the screen, but later could be extended to grab the appropriate per-priority-level bo from the screen.

How useful this would be depends on how many contexts are created off a single screen, but I guess w/ the browser that could be a lot.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: mesa/mesa#25