Attention is currently required from: laforge, neels.

pespin has posted comments on this change. ( 
https://gerrit.osmocom.org/c/osmo-hnbgw/+/36539?usp=email )

Change subject: per-HNB GTP-U traffic counters via nft
......................................................................


Patch Set 13:

(2 comments)

Patchset:

PS6:
> regarding split files, i kind of like that everything is contained in a 
> single .c file. […]
With thew new comments you added it's "good enough" because one can clearly see 
which thread executes that function, so we can merge it this way for now.
My point is that, precisely, if you put all the nft thread in a seprate file, 
it suddenly becomes clear that all that code belongs to that thread, and you 
don't need to go marking each function specifying who runs it.
Furthermore, it becomes easier to follow interaction of 2 threads by having one 
file open by the side of the other one.


File src/osmo-hnbgw/nft_kpi.c:

https://gerrit.osmocom.org/c/osmo-hnbgw/+/36539/comment/3ecb5f62_9a8da3da
PS12, Line 694:         unsigned long period_us = osmo_tdef_get(hnbgw_T_defs, 
-34, OSMO_TDEF_US, 1000000);
> ah yes this is exactly what i thought
yes, this is simple, usual in code, so I'm not asking something out of this 
world I think. Feel free to submit as a follow-up patch, but I definetly think 
this should be merged soon after this patch is merged.



--
To view, visit https://gerrit.osmocom.org/c/osmo-hnbgw/+/36539?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: Ib2f0a9252715ea4b2fe9c367aa65f771357768ca
Gerrit-Change-Number: 36539
Gerrit-PatchSet: 13
Gerrit-Owner: neels <[email protected]>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <[email protected]>
Gerrit-Reviewer: pespin <[email protected]>
Gerrit-Attention: neels <[email protected]>
Gerrit-Attention: laforge <[email protected]>
Gerrit-Comment-Date: Thu, 23 May 2024 15:48:41 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: neels <[email protected]>
Comment-In-Reply-To: pespin <[email protected]>
Gerrit-MessageType: comment

Reply via email to