unified-memory-framework icon indicating copy to clipboard operation
unified-memory-framework copied to clipboard

A library for constructing allocators and memory pools. It also contains broadly useful abstractions and utilities for memory management. UMF allows users to manage multiple memory pools characterized...

Results 167 unified-memory-framework issues
Sort by recently updated
recently updated
newest added

### Description ### Checklist - [ ] Code compiles without errors locally - [ ] All tests pass locally - [ ] CI workflows execute properly - [ ] CI...

UMF should offer a set of observability functions that can be used to retrieve the memory properties of memory allocated through UMF. Since these properties are closely tied to the...

enhancement
1.0 API readiness

fixes: #1078 ### Description ### Checklist - [ ] Code compiles without errors locally - [ ] All tests pass locally - [ ] CI workflows execute properly - [...

memspace api will not be production ready/stable for 1.0 release. With 1.0 we have clearly mark part's of umf which are unstable and can be changed in not backward compatible...

1.0 API readiness

Our OPS structures for pools and providers are currently not backward compatible, even though they include a `version` field. The following are four separate requirements we must fulfill: 1. **User...

1.0 API readiness

# Add variadic arguments API This issue introduces generic CTL API for the following functions: ```cpp umfCtlGet(const char* name, ...); umfCtlSet(const char* name, ...); umfCtlexec(const char* name, ...); ``` Current...

1.0 API readiness

Some umf destroy functions returns void: e.g.umfMemoryProviderDestroy, umfDisjointPoolSharedLimitsDestroy, others return umf_result e.g. umfDisjointPoolParamsDestroy we should decide a one approach, to return value of the destruction functions, and unify it.

bug
1.0 API readiness

Other pools uses default config(tbh only jmalloc, and disjoint uses any parameters). For sure we should not throw seqfault. as easy fix can just return einval, but we might consider...

bug
high priority

## Rationale Today the params of the disjoint pool are initialized with nulls. We need to agree on meaningful default parameters and mention it in the documentation. ## API Changes...

enhancement
high priority

A race condition occurs when the scalable pool is destroyed while another thread is performing Thread-Local Storage (TLS) destruction. This issue arises only if one thread is in its TLS...

bug
high priority