diff options
| author | Andreas Eversberg <jolly@eversberg.eu> | 2023-10-09 13:08:50 +0200 |
|---|---|---|
| committer | Oliver Smith <osmith@sysmocom.de> | 2023-12-11 10:43:08 +0100 |
| commit | 3a3e544a39fb3f60f91c554d17a3c7692beb7f26 (patch) | |
| tree | f75bd0cd90596c3daac1f8ac2bf670ab4ac42ab5 | |
| parent | 49a59675b1044280ee5a0e9402693bb225ef64cb (diff) | |
Increase RR scheduler priority to 20, to avoid dropped bursts
This has been fixed in osmo-bts too.
If frames are not deliverd fast enough to the DSP, bursts will get
dropped. The osmo-bts-sysmo process must have priority over other
processes, so it can deliver frames fast enough.
Related: OS#6199
Change-Id: Ifa2c36bc0975e89d21b6fb2fc49db6077e5207da
(cherry picked from commit 952f5c7b9566aff2322fb226d23103bd503fa152)
| -rw-r--r-- | contrib/systemd/osmo-pcu.service | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contrib/systemd/osmo-pcu.service b/contrib/systemd/osmo-pcu.service index f688d7f3..521f6fc7 100644 --- a/contrib/systemd/osmo-pcu.service +++ b/contrib/systemd/osmo-pcu.service @@ -13,7 +13,7 @@ RestartSec=2 # CPU scheduling policy: CPUSchedulingPolicy=rr # For real-time scheduling policies an integer between 1 (lowest priority) and 99 (highest priority): -CPUSchedulingPriority=11 +CPUSchedulingPriority=20 # See sched(7) for further details on real-time policies and priorities [Install] |