You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2018/08/09 16:16:00 UTC

[jira] [Resolved] (ARROW-665) C++: Move zeroing logic for (re)allocations to the Allocator

     [ https://issues.apache.org/jira/browse/ARROW-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wes McKinney resolved ARROW-665.
--------------------------------
       Resolution: Won't Fix
    Fix Version/s: 0.10.0

Closing for now

> C++: Move zeroing logic for (re)allocations to the Allocator
> ------------------------------------------------------------
>
>                 Key: ARROW-665
>                 URL: https://issues.apache.org/jira/browse/ARROW-665
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Uwe L. Korn
>            Assignee: Uwe L. Korn
>            Priority: Major
>             Fix For: 0.10.0
>
>
> Instead of doing this in e.g. the builders, we should move this logic to the Allocator. For example, jemalloc provides a flag {{MALLOCX_ZERO}} to indicate that an allocated region should be zeroed. The POSIX API also provides the (sadly unaligned) {{calloc}} call that returns zeroed pages. 
> The speciality here is that the pages may already be zeroed by the OS for security reasons (i.e. so that one process does not see the content of the process that previously owned this page).



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