NotificationsYou must be signed in to change notification settings
Fork546
Star4.7k

Ignore memory management object for native alloc funcitons#3300

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Open

umar456 wants to merge3 commits intoarrayfire:master

base:master

Choose a base branch

fromumar456:native_mm_ignore_mm

Open

Ignore memory management object for native alloc funcitons#3300

umar456 wants to merge3 commits intoarrayfire:masterfromumar456:native_mm_ignore_mm

Conversation

Copy link

Member

umar456 commentedSep 29, 2022

This PR adds a new memory manager example and fixes the native alloc function so that it ignores the af_memory_manager object.

Description

Creates a new memory manager example
The native alloc and native free functions now ignore the af_memory_manager object because they now allocate on the current device.
Empty allocations on the CPU backend do not call the alloc function

Changes to Users

N/A

Checklist

Rebased on latest master
Code compiles
Tests pass
Functions added to unified API
Functions documented

umar456 added3 commits

September 29, 2022 09:03

The native alloc and free functions don't require MM object

64639ef

The native alloc and free functions are used to allocate and freefunctions. These functions do not need the memory manager implementationto work because they are just allocating directly with the underlyingbackend. This change will now ignore the memory manager objectwhen allocating the memory.

Avoid allocating memory with the CPU backend for empty Array<T>

a993a21

Create a new memory manager example

b620008