Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Trilinos
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • 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
  • #3445

Closed
Open
Created Sep 14, 2018 by James Willenbring@jmwilleMaintainer

ThreadPool: Removal of ThreadPool from Trilinos

Created by: kddevin

@trilinos/stk @trilinos/framework @bartlettroscoe

Expectations

Soon we will remove ThreadPool from the Trilinos code base. Users of ThreadPool should respond to this issue ASAP with questions/concerns.

Within Trilinos, STKClassic depends on ThreadPool; STKClassic is also targeted for removal #3444 (closed) .
STKSearch claims a dependence on ThreadPool, but, in truth, does not need it; this claim of dependence will be removed.

Motivation and Context

ThreadPool is no longer supported; it has been replaced by the far superior Kokkos toolkit. Users of ThreadPool can migrate to Kokkos.

Removing unsupported, obsolete code is necessary to effectively maintain the Trilinos code base.

Definition of Done

ThreadPool removed from stk_search dependencies ThreadPool source code removed STKClassic source code removed STK/Trilinos integration and testing completed

Possible Solution

Removal of ThreadPool is preferred. If, for some reason, #3444 (closed) cannot be done, ThreadPool will move into the stk_classic directory to prevent further adoption by applications.

Related Issues

  • Is blocked by #3444 (closed)
Assignee
Assign to
Time tracking