Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

using ManagedArray::reallocate() on a default-constructed ManagedArray doesn't actually allocate at all #90

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

wrtobin
Copy link

@wrtobin wrtobin commented Oct 30, 2019

No description provided.

…st case to ensure realloc on preallocated managed arrays copies over data correctly, also implement a fix for the realloc bug
{
chai::ManagedArray<float> array;
array.reallocate(1);
float val = array[0];
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This causes a segfault in the current implementation, as the ManagedArray doesn't actually allocate anything during the reallocate call.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

changes look reasonable to me.

@wrtobin
Copy link
Author

wrtobin commented Oct 30, 2019

Note I haven't checked for all tests passing on Lassen yet -- since the machine is still down at the moment.

pointer_record->m_user_callback(ACTION_ALLOC, ExecutionSpace(space), sizeof(T) * elems);
void* new_ptr = m_allocators[space]->allocate(sizeof(T)*elems);
pointer_record->m_user_callback(ACTION_ALLOC, ExecutionSpace(space), sizeof(T) * elems);
void* new_ptr = m_allocators[space]->allocate(sizeof(T)*elems);
Copy link
Contributor

@robinson96 robinson96 Oct 30, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good, wait for David or Adam to approve as well.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will cause reallocate to allocate a pointer in every space - I'm not sure that's what we want.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wrtobin @robinson96 - I think this PR introduces an unexpected change in behavior, can you take a look?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ooh - you're right David.
Bill, the model should preserve lazy allocation of device memory so that reallocations don't inadvertently initialize device memory if they haven't used gpu memory before. At one point, we had an implementation of reallocate that also strode to only do a deep copy of the data on any memory space where the data was active.

Copy link
Member

@davidbeckingsale davidbeckingsale left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having reallocate always allocate pointers in all spaces changes the memory usage of reallocated arrays. @robinson96 do you agree?

pointer_record->m_user_callback(ACTION_ALLOC, ExecutionSpace(space), sizeof(T) * elems);
void* new_ptr = m_allocators[space]->allocate(sizeof(T)*elems);
pointer_record->m_user_callback(ACTION_ALLOC, ExecutionSpace(space), sizeof(T) * elems);
void* new_ptr = m_allocators[space]->allocate(sizeof(T)*elems);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will cause reallocate to allocate a pointer in every space - I'm not sure that's what we want.

@robinson96 robinson96 self-requested a review November 18, 2019 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants