You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Todd Farmer (Jira)" <ji...@apache.org> on 2022/07/12 14:05:02 UTC

[jira] [Assigned] (ARROW-11916) [C++] Investigate signal-safe spin lock

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

Todd Farmer reassigned ARROW-11916:
-----------------------------------

    Assignee:     (was: Antoine Pitrou)

This issue was last updated over 90 days ago, which may be an indication it is no longer being actively worked. To better reflect the current state, the issue is being unassigned. Please feel free to re-take assignment of the issue if it is being actively worked, or if you plan to start that work soon.

> [C++] Investigate signal-safe spin lock
> ---------------------------------------
>
>                 Key: ARROW-11916
>                 URL: https://issues.apache.org/jira/browse/ARROW-11916
>             Project: Apache Arrow
>          Issue Type: Task
>          Components: C++
>            Reporter: Antoine Pitrou
>            Priority: Minor
>
> Abseil claims to have a async-signal-safe spinlock class:
> https://github.com/abseil/abseil-cpp/blob/master/absl/base/internal/spinlock.h
> This could be used to implement rudimentary mutual exclusion between a signal handler and regular code that sets up or tears down shared resources used by the handler.
> The caveat is that signals need (apparently) to be blocked inside the handler before taking the spinlock.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)