Attention is currently required from: laforge, neels.
pespin has posted comments on this change. (
https://gerrit.osmocom.org/c/osmo-hnbgw/+/36385?usp=email )
Change subject: per-HNB GTP-U traffic counters via nft
......................................................................
Patch Set 17:
(1 comment)
Patchset:
PS3:
I think it makes a lot of sense to keep the patches
separate as they are. […]
osmo-trx: See trx_rate_ctr_timerfd_cb() and
CommonLibs/trx_rate_ctr.cpp in general.
See also dispatch_trx_rate_ctr_change().
osmo-trx is already heavily multithreaded so it's fine doing it that way since
it's already complex (it could have been done with an osmo_itq too). For other
programs not heavily multithread I'd avoid playing with mutexes and simply rely on
message passing integrated in the main loop.
Regarding own thread vs multithread: Anything running under the main loop which blocks the
main loop for long periods of time while waiting for some procedure to finish is broken by
design, be it 300ms, 500ms, 1s, 3s, 50000s.
Fine if you want to keep it in 2 patches, but I wouldn't merge this one until the
other one is ready and can be merged together.
--
To view, visit
https://gerrit.osmocom.org/c/osmo-hnbgw/+/36385?usp=email
To unsubscribe, or for help writing mail filters, visit
https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-hnbgw
Gerrit-Branch: master
Gerrit-Change-Id: I35b7e97fd039e36633dfde1317170527c82f9f68
Gerrit-Change-Number: 36385
Gerrit-PatchSet: 17
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Wed, 10 Apr 2024 08:30:48 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: neels <nhofmeyr(a)sysmocom.de>
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment