Skip to content

GitLab

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

Closed
Open
Created Dec 16, 2020 by Florian Schmaus@flowOwner

Anywhere queue could by implemented with reader/writer locks

The "anywhere queue" currently uses a mutex for enqueue and dequeue operations, which are fully locked using a std::mutex. It would be possible to use a reader/writer lock (std::shared_mutex in CPP): This would allow the dequeue operation to only take the reader lock first, and bail out if the queue is empty. We could even consider using boost's UpgradeLockable, which is a upgradable reader/writer lock.

Assignee
Assign to
Time tracking