Skip to content

Redo memory strategy based of single-address space reserve mapping for the process #43

Open
@Ed94

Description

MS Blog

This came about from doing Handmade Hero along with studying other content from the community.

Going to change the allocators to use a single address space, I'll reserve a mapping for with a max limit. The limit will be set via the gencpp::init along with the initial commit space. Default will be 4gb reserve and 1 gb commit.

The program will share a single address space for everything based on this commit so I'll offset the different general use cases for memory by that:

  • Persistent ( Globals & String Cache )
  • Code Transients ( AST & Parser Token Pools )
  • String Transients ( dynamic strings )
  • File Transients ( Bulk content read / write )

I'll hold off on this though until we have the dependent data allocation strategies down pact with regular heap allocation.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    performanceAnything related to bad performance issue or a beneficial optimization

    Projects

    • Status

      Todo

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions