Attention is currently required from: pespin, fixeria, dexter.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-pcu/+/31341 )
Change subject: pcu_l1_if_phy: flexible phy access
......................................................................
Patch Set 9:
(1 comment)
Patchset:
PS9:
> To me the BSC telling which phy driver to use looks really like BSC knowing about the PCU implementa […]
well, in the classic (12.21 based) information model, the BSC knows everything and it spreads its knowledge to the BTSs. And in case of BTS-colocated PCU, the BTS then passes things to the PCU (see how the NSVC are configured in osmo-bsc.cfg). In general I also like that, as it reduces the amount of things an operator needs to configure on each and every of their (potentially many) remote sites.
We might also get back to fixeria's idea in the meeting today: have separte binaries like osmo-pcu-{rbs,sysmo,...} to avoid the problem.
Many alternatives, I'm not deep enough into the topic to have a clear idea.
--
To view, visit https://gerrit.osmocom.org/c/osmo-pcu/+/31341
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-pcu
Gerrit-Branch: master
Gerrit-Change-Id: I8692d1bd5d137a17cf596ee2914722f419c9978d
Gerrit-Change-Number: 31341
Gerrit-PatchSet: 9
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Tue, 21 Feb 2023 14:18:57 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: neels, pespin.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-hnbgw/+/31431 )
Change subject: context map: introduce RUA and SCCP FSMs to fix leaks
......................................................................
Patch Set 5: Code-Review+1
(2 comments)
File include/osmocom/hnbgw/context_map.h:
https://gerrit.osmocom.org/c/osmo-hnbgw/+/31431/comment/ce2ee4d9_2f263045
PS5, Line 22: enum map_rua_fsm_event {
not critical, but this is where the ISO/OSI style request/indication naming could be useful to clearly see the direction of such an "event". the _RX_ are indications telling the FSM that something happens. Just like SCCP_DISC, HNB_LINK_LOST. Where TX_RANAP_MSG and _EV_PLEASE_DISCONNECT are requests to the FSM.
File src/osmo-hnbgw/hnbgw_rua.c:
https://gerrit.osmocom.org/c/osmo-hnbgw/+/31431/comment/3a993d43_7a99de14
PS5, Line 183: { RUA_ProcedureCode_id_Connect, "id-Connect" },
> AFAIK the messages are called "id-Connect" in RUA, including the "id-", whatever the meaning may be
No, the procdures are not called "id-Connect", but "CONNECT". See the section headlines of 25.468 9.1.x.
That "id-" some artefact of the asn.1 syntax, so they have differnt names for the identifier from the type name.
--
To view, visit https://gerrit.osmocom.org/c/osmo-hnbgw/+/31431
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-hnbgw
Gerrit-Branch: master
Gerrit-Change-Id: I6ff7e36532ff57c6f2d3e7e419dd22ef27dafd19
Gerrit-Change-Number: 31431
Gerrit-PatchSet: 5
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: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Tue, 21 Feb 2023 14:13:59 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Comment-In-Reply-To: neels <nhofmeyr(a)sysmocom.de>
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: neels.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-hnbgw/+/31428 )
Change subject: log tweak
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
> not sure we want that 'id-' prefix. That's just an artefact of auto-generated asn. […]
The procdures are not called "id-Connect", but "CONNECT". See the section headlines of 25.468 9.1.x.
That "id-" some artefact of the asn.1 syntax, so they have differnt names for the identifier from the type name.
--
To view, visit https://gerrit.osmocom.org/c/osmo-hnbgw/+/31428
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-hnbgw
Gerrit-Branch: master
Gerrit-Change-Id: Ib6f8c46355d4748089e59c80fc1c8c736c887a26
Gerrit-Change-Number: 31428
Gerrit-PatchSet: 1
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Comment-Date: Tue, 21 Feb 2023 14:04:40 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Gerrit-MessageType: comment
Attention is currently required from: pespin.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-hnbgw/+/31431 )
Change subject: context map: introduce RUA and SCCP FSMs to fix leaks
......................................................................
Patch Set 5:
(3 comments)
Patchset:
PS5:
> I find this all quite hard to review. […]
Maybe I can spend yet another hour to see if I can split off very simple things.
But to split is essentially asking to re-implement this from scratch. Not sure if we have enough hours left to spend on this topic for that.
Another idea is maybe i can place comments here in gerrit for each patch chunk?
i did initially have two patches, one adding the FSMs and one moving from oph to ranap msgb, but that was a bunch of new code being added, then changed again *a lot* in the patch following right after that. Squashing them made the patch volume shrink *a lot*, and makes *a lot* more sense when reading the code. I spent many hours on keeping the two patches separate, and it was a complete waste of time in the end, so I'm a bit frustrated with trying to do big refactoring in small patches now.
It's like asking to build a new house while some rotten moldy house is still standing in its place -- the new doors and windows will simply not fit in the old walls.
I would encourage to review by following the message pipeline:
- See that rua_to_scu() is now extremely simple.
- See that the osmo_scu_prim composition for SCCP messages has moved from hnbgw_rua.c to context_map_sccp.c, and follow the path of rua_to_scu() to osmo_sccp_user_sap_down().
- Notice that everything connection-oriented feeds into FSM events, and that their data arg is in OTC_SELECT.
The FSM charts are looking pretty complex too, not sure if it helps but I uploaded them for convenience:
https://people.osmocom.org/neels/veY1eiNg/hnbgw_context_map.pnghttps://people.osmocom.org/neels/veY1eiNg/hnbgw_context_map_fsm.png
File include/osmocom/hnbgw/context_map.h:
https://gerrit.osmocom.org/c/osmo-hnbgw/+/31431/comment/6418a045_cd84cdc8
PS5, Line 90: /* RUA contxt ID used in RUA messages to/from the hnb_gw. */
> context
thx
File src/osmo-hnbgw/hnbgw_rua.c:
https://gerrit.osmocom.org/c/osmo-hnbgw/+/31431/comment/945c7fef_a77231fe
PS5, Line 183: { RUA_ProcedureCode_id_Connect, "id-Connect" },
> Drop "id-" prefix
AFAIK the messages are called "id-Connect" in RUA, including the "id-", whatever the meaning may be
--
To view, visit https://gerrit.osmocom.org/c/osmo-hnbgw/+/31431
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-hnbgw
Gerrit-Branch: master
Gerrit-Change-Id: I6ff7e36532ff57c6f2d3e7e419dd22ef27dafd19
Gerrit-Change-Number: 31431
Gerrit-PatchSet: 5
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Tue, 21 Feb 2023 13:53:07 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: dexter.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-pcu/+/31361 )
Change subject: pcu_l1_if: use only the term "direct PHY access"
......................................................................
Patch Set 2: Code-Review+1
--
To view, visit https://gerrit.osmocom.org/c/osmo-pcu/+/31361
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-pcu
Gerrit-Branch: master
Gerrit-Change-Id: I121ad85cd8581c40f390dbaad0d6a028d68b095e
Gerrit-Change-Number: 31361
Gerrit-PatchSet: 2
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: msuraev <msuraev(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Tue, 21 Feb 2023 12:45:07 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: dexter.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-pcu/+/31438 )
Change subject: pcu_l1_if_phy: add new API call l1if_disconnect_pdch
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
So you are adding a new API but I see it used nowhere?
--
To view, visit https://gerrit.osmocom.org/c/osmo-pcu/+/31438
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-pcu
Gerrit-Branch: master
Gerrit-Change-Id: I4cc72f032f0abdd5833cdd3b1fe68c69394d89a4
Gerrit-Change-Number: 31438
Gerrit-PatchSet: 1
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Tue, 21 Feb 2023 12:44:39 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment