Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gstreamer gstreamer
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 675
    • Issues 675
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 354
    • Merge requests 354
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gstreamergstreamer
  • Issues
  • #382

Closed
Open
Created Apr 24, 2019 by Mats Lindestam@MatsContributor

GstElement: Need a way to prevent realtime priority to propagate to GStreamer threads (Enhancement)

We have a use case where we promote one or more pipelines from the Linux scheduling policy SCHER_OTHER to SCHER_RR. What we are trying to create a way to prevent the SCHER_RR policy to propagate to the pipeline internal threads.

We have made a patch in the file gstelement.c in the function gst_element_call_async_func that resets the scheduling policy from SCHER_RR to SCHER_OTHER. This patch works but we are not sure that this is the proper way.

0001-Prototype-hack-for-realtime-priority-in-parent-threa.patch

We would like to discuss a permanent solution.

GStreamer version: 1.14.0 Operating system: Linux

Assignee
Assign to
Time tracking