[ 
https://issues.apache.org/jira/browse/ARROW-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792802#comment-16792802
 ] 

Pearu Peterson commented on ARROW-4861:
---------------------------------------

No. As discussed in ARROW-2447 , a Device would not be a good representative of 
a memory address origin. In certain cases (Managed Memory, Pinned/Host Memory), 
the memory address would be accessible from both CPU as well as from device.

A virtual address space should be considered as a notation where only one set 
of memory management operations (allocation, deallocation, copy, memset, fill, 
etc) can be applied.

MemoryPool would be a better representative (than Device) of a virtual address 
space that contains addresses pointing to memories of different devices. 
Although at hardware/driver level the addresses will be translated to the 
actual addresses of device memories, these translations are transparent to 
Arrow processes.

> [C++] Introduce MemoryPool::Memset method.
> ------------------------------------------
>
>                 Key: ARROW-4861
>                 URL: https://issues.apache.org/jira/browse/ARROW-4861
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Pearu Peterson
>            Assignee: Pearu Peterson
>            Priority: Major
>              Labels: C++
>
> One can define a device MemoryPool subclass (say, CudaMemoryPool) that can be 
> used for creating a Buffer representing a device memory. The prerequisite for 
> this to work is that all Buffer memory operations (allocation, deallocation, 
> reallocation, etc) can be redefined to use the corresponding device specific 
> operations. No host specific operation would be allowed as the device memory 
> would be inaccesible from host.
> Currently, this is almost possible. Namely, `Buffer::ZeroPadding` uses host 
> specific `memset` function for zero-padding the allocated Buffer memory.
> Suggestion: introduce a new method `MemoryPool::Memset` that 
> `Buffer::ZeroPadding` can use.
> The Memset method would use `memset` by default but device specific 
> MemoryPool subclasses can override the method to use device driver version of 
> the memset function.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to