Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Trilinos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 936
    • Issues 936
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • James Willenbring
  • Trilinos
  • Issues
  • #384

Closed
Open
Created May 23, 2016 by James Willenbring@jmwilleMaintainer

Tpetra::DistObject: Expose nonblocking versions of doExport & doImport

Created by: mhoemmen

@trilinos/tpetra

Epic: #767.

Expose nonblocking versions of doExport and doImport in Tpetra::DistObject. These comprise Tpetra's public interface for data redistribution, so this would expose nonblocking redistribution to users.

Tpetra uses the DistObject methods doImport and doExport, called on MultiVector objects, to handle communication for sparse matrix-vector multiplication. Some preconditioners, such as those in Ifpack2, may also do so in their apply() methods. Thus, if we want to overlap communication and computation, the best place to start is by making doImport and doExport nonblocking.

In an interface sense, this is independent of #383. However, best performance benefits would come from fixing #383 first.

Assignee
Assign to
Time tracking