hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Jungblut (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HAMA-546) Add access to remote memory
Date Mon, 14 May 2012 07:15:49 GMT

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

Thomas Jungblut commented on HAMA-546:
--------------------------------------

Yeah integration is key :)

bq. Should the key for retrieval be a function of both the userKey and superstep count in
which the value is computed?

I think we should provide another implementation like a SuperstepMap where you can store things
like this thoughout superstep numbers.

bq. Which implies should we support retrieval only for values in the previous superstep or
should we support values for all the supersteps?

Both is possible, because you can have many caches, all doing different implementation dependend
things.
We should just try to make this as simple as possible.
                
> Add access to remote memory
> ---------------------------
>
>                 Key: HAMA-546
>                 URL: https://issues.apache.org/jira/browse/HAMA-546
>             Project: Hama
>          Issue Type: New Feature
>          Components: bsp core
>            Reporter: Thomas Jungblut
>            Assignee: Thomas Jungblut
>         Attachments: HAMA-546_1.patch
>
>
> bsp_get and bsp_put are integral parts of the BSP computing model.
> They are defined as follows:
> bsp_get [1]
> {quote}
>      The bsp_get(3) and bsp_hpget(3) operations  reach  into  the
>      local   memory   of  another  process  and  copy  previously
>      registered remote data held there into a data  structure  in
>      the local memory of the process that initiated them.
> {quote}
> bsp_put [2]
> {quote}
>      The aim of bsp_put(3) and  bsp_hpput(3)  is  to  provide  an
>      operation  akin  memcpy(3C) available in the Unix <string.h>
>      library.  Both operations copy a specified number of  bytes,
>      from  a byte addressed data structure in the local memory of
>      one process into contiguous memory locations  in  the  local
>      memory of another process. The distinguishing factor between
>      these operations is provided by the buffering choice.
> {quote}
> A very simple implementation can be based on a HashMap on every peer which can be obtained
via RPC. 
> In this case we need to extend the MessageManager to be able to do off-the-band communication.
> It would be great to extract a common interface which can be inter-operable with other
caching tools like DirectMemory or EHCache. 
> [1] http://www.bsp-worldwide.org/implmnts/oxtool/man/bsp_get.3.html
> [2] http://www.bsp-worldwide.org/implmnts/oxtool/man/bsp_put.3.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message