Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • VILLASnode VILLASnode
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 28
    • Issues 28
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 6
    • Merge requests 6
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ACS
  • Public
  • VILLASframework
  • VILLASnodeVILLASnode
  • Issues
  • #176

Closed
Open
Created Jul 15, 2018 by Dennis Potter@dennis.potter

Clean up old memory pools in infiniband node

There are some old buffer pools and functions which I used to run communication of data between nodes. There is no need for these functions anymore since everything is implemented in ib_read() and ib_write(), and since we are using the buffers allocated by the framework.

@stvogel: before I delete the code, I want to make sure we really don't need it.

Can you think of any scenario where we need other communication than meta + data (like we have now)?

The only scenario I could think of, is that a node fetches status data of another node with IBV_WR_RDMA_READ (which reads from the remote memory without remote kernel intervention). This would require the exchange of address/key-pairs with IBV_WR_SEND beforehand.

(For this particular functionality I would reuse the functions, but pools are overkill.)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking