Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 13 Sep 2013 20:29:52 +0000 (UTC)
From: "Chris Nauroth (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12661007.1375311402427.131592.1379104192432@arcas>
In-Reply-To: <JIRA.12661007.1375311402427@arcas>
References: <JIRA.12661007.1375311402427@arcas>
Subject: [jira] [Commented] (HDFS-5049) Add JNI mlock support
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chris Nauroth commented on HDFS-5049:
-------------------------------------

bq. I think it probably makes sense to just add a long NativeIO#getMemlockLimit function, and let the JNI layer take care of the details.

+1 for the proposal.

bq. I'll file a follow-up JIRA for this in a moment... or perhaps I should file two follow-up JIRAs, one for Windows support?

I think 2 separate issues makes sense.  It will be easier to code review each change in isolation.
                
> Add JNI mlock support
> ---------------------
>
>                 Key: HDFS-5049
>                 URL: https://issues.apache.org/jira/browse/HDFS-5049
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode, namenode
>            Reporter: Colin Patrick McCabe
>            Assignee: Andrew Wang
>         Attachments: hdfs-5049-1.patch
>
>
> Add support for {{mlock}} and {{munlock}}, for use in caching.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira