Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • L libnice
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • libnice
  • libnice
  • Issues
  • #1
Closed
Open
Issue created Jun 05, 2018 by Philip Withnall@pwithnallReporter

Lock contention in critical path

Submitted by Philip Withnall @pwithnall

Assigned to Philip Withnall @pwithnall

Link to original bug (#93)

Description

(Migrated from Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=26912)

There is contention on the libnice global lock in the critical path, that is the path taken to send and receive packets. These paths should not take that lock. There should probably a per-component lock that protects the required data.. Even if that means copying these fields.

Assignee
Assign to
Time tracking