Skip to content
Snippets Groups Projects
Select Git revision
  • c355bd93271557f241ab1c1095fcab7cfd744097
  • develop default protected
  • feature/gmsh-reader
  • feature/reconstruction
  • save_clemence
  • origin/stage/bouguettaia
  • feature/kinetic-schemes
  • feature/local-dt-fsi
  • feature/composite-scheme-sources
  • feature/composite-scheme-other-fluxes
  • feature/serraille
  • feature/variational-hydro
  • feature/composite-scheme
  • hyperplastic
  • feature/polynomials
  • feature/gks
  • feature/implicit-solver-o2
  • feature/coupling_module
  • feature/implicit-solver
  • feature/merge-local-dt-fsi
  • master protected
  • v0.5.0 protected
  • v0.4.1 protected
  • v0.4.0 protected
  • v0.3.0 protected
  • v0.2.0 protected
  • v0.1.0 protected
  • Kidder
  • v0.0.4 protected
  • v0.0.3 protected
  • v0.0.2 protected
  • v0 protected
  • v0.0.1 protected
33 results

pugs

Stéphane Del Pino's avatar
Stéphane Del Pino authored
Also change the semantic/implementation of sub-Array and sub-Table
views. One does not use anymore Kokkos' subView which seems to be very
expensive (2 to 3 times the cost for the Lagrangian acoustic solver if
one uses subView for connectivity: lists of sub-items). It looks like
the over cost is related to the memory management (here the reference
counting).

Sub-Array and sub-Table view are coarsely "embedded raw
pointers" (which may not be safe as it is the case in
Kokkos::StaticCrsGraph). However we tried to reduce the risk of having
a view on a destroyed Array/Table by forbidding copy constructors.

ConnectivityMatrix and ItemToItemMatrix still require refactoring. For
instance it would be natural for ItemToItemMatrix  to be replaced by
the appropriate SubItemValuePerValue<ItemId>.
c355bd93
History
Name Last commit Last update