You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Rei Odaira (JIRA)" <ji...@apache.org> on 2016/06/03 16:29:59 UTC

[jira] [Assigned] (CASSANDRA-11576) Add support for JNA mlockall(2) on POWER

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

Rei Odaira reassigned CASSANDRA-11576:
--------------------------------------

    Assignee: Rei Odaira

> Add support for JNA mlockall(2) on POWER
> ----------------------------------------
>
>                 Key: CASSANDRA-11576
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11576
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>         Environment: POWER architecture
>            Reporter: Rei Odaira
>            Assignee: Rei Odaira
>            Priority: Minor
>             Fix For: 2.1.x, 2.2.x, 3.0.x, 3.x
>
>         Attachments: 11576-2.1.txt
>
>
> org.apache.cassandra.utils.CLibrary contains hard-coded C-macro values to be passed to system calls through JNA. These values are system-dependent, and as far as I investigated, Linux and AIX on the IBM POWER architecture define {{MCL_CURRENT}} and {{MCL_FUTURE}} (for mlockall(2)) as different values than the current hard-coded values.  As a result, mlockall(2) fails on these platforms.
> {code}
> WARN  18:51:51 Unknown mlockall error 22
> {code}
> I am going to provide a patch to support JNA mlockall(2) on POWER.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)