Attention is currently required from: fixeria, osmith.

Hello Jenkins Builder, fixeria, pespin,

I'd like you to reexamine a change. Please visit

https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/40153?usp=email

to look at the new patch set (#2).

The following approvals got outdated and were removed: Code-Review+1 by fixeria

Change subject: bts: set osmo-bts sched priority to 30 ......................................................................

bts: set osmo-bts sched priority to 30

Change the scheduling priority from 10 to 30, as we are currently see osmo-bts suffering from scheduling latency in jenkins even though we don't run other jobs at that time:

20250425034138405 DL1C ERROR PC clock skew: elapsed_us=387574, error_us=382959 (scheduler_trx.c:449)

This should fix that the kernel prioritizes other (userspace or kernel) processes running on the same machine that have a higher priority. We have seen such an improvement after increasing scheduler priority for osmo-bts-sysmo too (see I2394e6bbc00a1d47987dbe7b70f4b5cbedf69b10).

Priority 30 is higher than 10. From sched(7):

Processes scheduled under one of the real-time policies (SCHED_FIFO, SCHED_RR) have a sched_priority value in the range 1 (low) to 99 (high).

This testsuite currently gets executed through docker-playground and it fetches this config from osmo-ttcn3-hacks (see If15461240f3037c142c176fc7da745a1701ae3f8).

Related: osmo-ci I0162f7299c8e37f893ffa10ddc4c8edece29ed7f Change-Id: I828422e2363a58ca8c19d0f1b8a1b7d4e4bc031e --- M bts/osmo-bts.cfg 1 file changed, 1 insertion(+), 1 deletion(-)

git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/53/40153/2