Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • openfpm_data openfpm_data
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Sbalzarini Lab
    • SSoftware
    • PParallel Computing
  • OpenFPM
  • openfpm_dataopenfpm_data
  • Wiki
  • Home

Home · Changes

Page history
Updated Home (markdown) authored May 03, 2015 by Pietro Incardona's avatar Pietro Incardona
Hide whitespace changes
Inline Side-by-side
Home.md
View page @ 76159d0f
......@@ -14,4 +14,4 @@ Example suppose to have a program that modularize each task (each task is a comp
To introduce the OpenFPM modularization we will introduce first the task and than the component inside OpenFPM that implement it.
OpenFPM at most basic level operations manage the **Memory**: getting some chunk of memory, destroy it, or resize it on any devices or with particular properties. The component inside OpenFPM designed to do such task is **devices (Memory)**. After that we have the capabilities to create memory we have to shape it, or give to them some meaning. More specifically we want to **Map** complex structures on memory, like a Grid, Vectors, Graph ... The component designed to do such task in OpenFPM is ** data **. While data implement complex structures on single machine, we would like to have distributed version of such complex structures. . After that we have complex structure, we would like to create distributed structures
OpenFPM at most basic level operations manage the **Memory**: getting some chunk of memory, destroy it, or resize it on any devices or with particular properties. The component inside OpenFPM designed to do such task is **devices (Memory)**. After that we have the capabilities to create memory we have to shape it, or give to them some meaning. More specifically we want to **Map** complex structures on memory, like a Grid, Vectors, Graph ... The component designed to do such task in OpenFPM is ** data **. While ** data ** implement complex structures on single machine, we would like to have distributed version of such complex structures. The component designed to do such task in OpenFPM is ** pdata **. Here pdata does not directly depend on data, but there is an intra-modularity between them given by Vcluster. Why we need this ? There are several reasons, the first is modularization of the comunication libraries
Clone repository
  • Basic objects
  • Home
  • Iterators
  • Memory mappings
  • Memory objects
  • Template order