Change in osmo-gsm-tester[master]: ms-srs: change the cpu governor before launching the ms.
gerrit-no-reply at lists.osmocom.org
Tue Jun 8 16:39:20 UTC 2021
alealcon has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-gsm-tester/+/24270 )
Change subject: ms-srs: change the cpu governor before launching the ms.
Patch Set 1:
Answering your questions:
- True. I didn't remember that problem. We should find a solution for this. It would be nice if it can be configured at the test setup, for every resource that it is using, going back to normal at the test teardown. Is that possible in a safe way (maybe setting a lock on the run_node while the test is executing that forces other OGT instances to wait for the lock release)?
- It isn't related to specific hosts. It can be any host that it's running under Linux (we currently use it for the ms-srs). It's a nice feature to allow the device to "full performance" during the test and going back to normal after the test is finished. I think it suits more to be a "run_node" property rather than a binary (enb-srs, ms-amarisoft, epc-srs...).
If it's too hard, we can start with the easiest solution that is to set the governor to performance as the default. What do you think, Andre?
In the future we can try to solve it, so we can get this feature. I think it's a cool one 😄
To view, visit https://gerrit.osmocom.org/c/osmo-gsm-tester/+/24270
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Owner: alealcon <alejandro.leal at srs.io>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: srs_andre <andre at softwareradiosystems.com>
Gerrit-CC: pespin <pespin at sysmocom.de>
Gerrit-Comment-Date: Tue, 08 Jun 2021 16:39:20 +0000
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the gerrit-log