This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
pespin gerrit-no-reply at lists.osmocom.orgpespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-gsm-tester/+/17847 ) Change subject: enb: Implement initial RF emulation API ...................................................................... Patch Set 2: > Patch Set 2: > > Just another thing that came to my mind Pau. The example handover.py test looked to me like the gain control is executed in the main processing loop. But how would you do that in the case you have an iperf client running in parallel. Usually, this would be in the main loop so the the gain control loop needs to run in a background thread. iperf can run in the background with no issue while the test changes the parameters. Right now we are using proc.launch_sync() for convinience, but you can simply launch() and then poll from time to time to check if the process is done or not. No need for different threads, the event loop cares take of everything. -- To view, visit https://gerrit.osmocom.org/c/osmo-gsm-tester/+/17847 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-gsm-tester Gerrit-Branch: master Gerrit-Change-Id: Ie98a3fb9bcd2b87b96ecbb5b79e0f53981892a32 Gerrit-Change-Number: 17847 Gerrit-PatchSet: 2 Gerrit-Owner: pespin <pespin at sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge at osmocom.org> Gerrit-Reviewer: pespin <pespin at sysmocom.de> Gerrit-Reviewer: srs_andre <andre at softwareradiosystems.com> Gerrit-Comment-Date: Sat, 18 Apr 2020 20:19:36 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: No Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20200418/823968eb/attachment.htm>