Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • PRRT PRRT
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 41
    • Issues 41
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LARN
  • PRRTPRRT
  • Issues
  • #52
Closed
Open
Created Dec 08, 2020 by Sven Liefgen@s8svliefDeveloper

Review concurrency

The C code didn't use locks for a lot of accesses on the socket, which seems to be correct, as they only ever occur in one thread. However in Rust, each field that is written to has to be in a Mutex. The Mutex overhead could probably be omitted by using unsafe code to get mutable references without a Mutex.

Assignee
Assign to
Time tracking