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/libosmocore/+/21047 ) Change subject: tdef: Introduce OSMO_TDEF_US unit ...................................................................... Patch Set 1: > Patch Set 1: Code-Review+1 > > well, the question is whether or not our usual programming environment can ever properly implement sub-ms timers. But sure, we can permit defining them... It can since timer scheduling can be done with microseconds. Regarding latency, I agree for a few microseconds it would probably be too much, but we are talking a thousand microseconds here, so we should be fine (but still allowing to express 1.7 ms instead of 2ms, or 0.9 instead of 1). So low values together with a proper schedule policy should be fine I guess (and have a separate main loop in a different thread for it if needed). -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/21047 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: I71848d7c1ee0649929ce07680ee7320bb2a42f0e Gerrit-Change-Number: 21047 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin at sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: daniel <dwillmann at sysmocom.de> Gerrit-Reviewer: laforge <laforge at osmocom.org> Gerrit-Reviewer: neels <nhofmeyr at sysmocom.de> Gerrit-Comment-Date: Mon, 09 Nov 2020 11:38:58 +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/20201109/c194630c/attachment.htm>