Skip to content
A memory allocator that automatically reduces the memory footprint of C/C++ applications.
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
src libmesh: fix warnings around pthread_exit not returning Mar 24, 2019
support
theory Typo fixes. Feb 18, 2019
.clang-format
.dockerignore
.editorconfig
.gitignore test: large-alloc stress test program from #36 Mar 7, 2019
.gitmodules use upstream Heap-Layers from Emery's repo Feb 23, 2018
AUTHORS
Dockerfile
GNUmakefile test: large-alloc stress test program from #36 Mar 7, 2019
LICENSE
Makefile
README.md
configure

README.md

Mesh: Compacting Memory Management for C/C++

Mesh is a drop in replacement for malloc(3) that compacts the heap without rewriting application pointers.

Mesh is described in an academic paper (arxiv PDF) that will appear at PLDI 2019.

Mesh runs on Linux; macOS support should be considered alpha-quality, and Windows is a work-in-progress.

Mesh has a standard C++ build process, and has no runtime dependencies other than libc-related libs:

$ git clone --recurse-submodules https://github.com/plasma-umass/mesh
$ cd mesh
$ ./configure; make; sudo make install
# example: run git with mesh as its allocator:
$ LD_PRELOAD=libmesh.so git status

More docs coming soon, but please open up an issue if you have questions (or issues)!

Implementation Overview

Mesh is built on Heap Layers, an infrastructure for building high performance memory allocators in C++ (see paper for details.)

The entry point of the library is libmesh.cc. This file is where malloc, free and the instantiations of the Heap used for allocating program memory lives.

DEFINITIONS

  • Page: The smallest block of memory managed by the operating system, 4Kb on most architectures. Memory given to the allocator by the operating system is always in multiples of the page size, and aligned to the page size.
  • Span: A contiguous run of 1 or more pages. It is often larger than the page size to account for large allocations and amortize the cost of heap metadata.
  • Arena: A contiguous range of virtual address space we allocate out of. All allocations returned by malloc(3) reside within the arena.
  • GlobalHeap: The global heap carves out the Arena into Spans and performs meshing.
  • MiniHeap: Metadata for a Span -- at any time a live Span has a single MiniHeap owner. For small objects, MiniHeaps have a bitmap to track whether an allocation is live or freed.
  • ThreadLocalHeap: A collections of MiniHeaps and a ShuffleVector so that most allocations and free(3)s can be fast and lock-free.
  • ShuffleVector: A novel data structure that enables randomized allocation with bump-pointer-like speed.
You can’t perform that action at this time.