Attention is currently required from: pespin.
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-upf/+/28244
to look at the new patch set (#4).
Change subject: add pfcp_endpoint
......................................................................
add pfcp_endpoint
Related: SYS#5599
Change-Id: Ic8d42e201b63064a71b40ca45a5a40e29941e8ac
---
M include/osmocom/pfcp/Makefile.am
A include/osmocom/pfcp/pfcp_endpoint.h
M include/osmocom/pfcp/pfcp_msg.h
M src/libosmo-pfcp/Makefile.am
A src/libosmo-pfcp/pfcp_endpoint.c
5 files changed, 585 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-upf refs/changes/44/28244/4
--
To view, visit https://gerrit.osmocom.org/c/osmo-upf/+/28244
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-upf
Gerrit-Branch: master
Gerrit-Change-Id: Ic8d42e201b63064a71b40ca45a5a40e29941e8ac
Gerrit-Change-Number: 28244
Gerrit-PatchSet: 4
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-MessageType: newpatchset
Attention is currently required from: pespin.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-upf/+/28244 )
Change subject: add pfcp_endpoint
......................................................................
Patch Set 3:
(12 comments)
File include/osmocom/pfcp/pfcp_endpoint.h:
https://gerrit.osmocom.org/c/osmo-upf/+/28244/comment/93090be2_bb694c9f
PS3, Line 46: * \param req If m is a PFCP Response to an earlier Request, req is that request message. */
> otherwise NULL?
ACK
https://gerrit.osmocom.org/c/osmo-upf/+/28244/comment/b26326e0_b8dbcd82
PS3, Line 51: struct osmo_pfcp_endpoint {
> osmo_pfcp_endp seems like it's going to be a typing/reading change worth it ;)
you mean the name should change to "osmo_pfcp_endp"?
Can we focus on functional code review please?
https://gerrit.osmocom.org/c/osmo-upf/+/28244/comment/8a4acdbf_c118bd79
PS3, Line 104:
> In general I'm missing some APIs to set callbaks, local_node_id, etc.
Do you mean add getters and setters?
I'm not going to add API bloat for each struct member.
File src/libosmo-pfcp/pfcp_endpoint.c:
https://gerrit.osmocom.org/c/osmo-upf/+/28244/comment/acdc991e_d2e57507
PS3, Line 42: struct osmo_pfcp_msg *m;
> Doesn't m already have a backpointer to ep? May make more sense to just have that one.
no, osmo_pfcp_msg has no pointer to an endpoint. Also it shouldn't.
https://gerrit.osmocom.org/c/osmo-upf/+/28244/comment/5742e43e_b272eaa5
PS3, Line 44: struct osmo_timer_list t1;
> This can be probably optimized to be only 1 timer per list, by moving them to the end of the list wh […]
that's the point of the osmo_timer API: it keeps a list and waits for the first entry, later timers untouched behind it in the list.
(Recently I was surprised to see load caused by timers triggering every 10th of a second; then again that was multiplied by number of active lchans. PFCP messages are more like 5 seconds timeouts, and not firing continuously. I see no need to optimize here.)
https://gerrit.osmocom.org/c/osmo-upf/+/28244/comment/56b3267e_a26eaee5
PS3, Line 73: int osmo_pfcp_queue_destructor(struct osmo_pfcp_queue_entry *qe)
> why is the destructor not static?
don't know why.
it should be static, thanks.
https://gerrit.osmocom.org/c/osmo-upf/+/28244/comment/3b53c02e_acea9681
PS3, Line 81: { .T = -19, .default_val = 15, .unit = OSMO_TDEF_S,
> why some timers have names and some don't?
there is no reason why.
We use magic numbers for T = N almost everywhere in osmocom.
But setting names made me notice a mistake, 27 should be 21, thx
https://gerrit.osmocom.org/c/osmo-upf/+/28244/comment/c96a3198_e3edf700
PS3, Line 122: /* time() returns seconds since 1970 (UNIX epoch), but the recovery_time_stamp is coded in the NTP format, which is
> you can check open5gs code, iirc some stuff exists to handle ntp timestamps and I also added some bi […]
i'm pretty unsure about this timestamp coding, just know that wireshark ended up showing the expected date.
do you have more specific code pointers?
Or even, is there API I can call instead of re-implementing?
OTOH the accuracy of the timestamp isn't really important AFAICT, the point of this is to have a unique value per application restart, for peers to detect that the peer has lost its state since last time. It's not critical to get this perfectly accurate, at least not until someone complains about it.
https://gerrit.osmocom.org/c/osmo-upf/+/28244/comment/06ddc0a1_198c168d
PS3, Line 139: unsigned int ep_t1(struct osmo_pfcp_endpoint *ep)
> static
thx
https://gerrit.osmocom.org/c/osmo-upf/+/28244/comment/73368fa8_8cb857ce
PS3, Line 144: unsigned int ep_keep_resp(struct osmo_pfcp_endpoint *ep)
> static
thx
(I'm dreaming of a tool that tells us which unused #includes we have in .c and .h files, and which functions should be made static because used only in a single .c file... something like this should exist right? maybe the linter has such features??)
https://gerrit.osmocom.org/c/osmo-upf/+/28244/comment/50760e6b_8c5b55fb
PS3, Line 177: static void pfcp_queue_timer_cb(void *data)
> Maybe rename to contain "expiry" in it?
"timer_cb" is consistent: for example in osmo_fsm, the name is timer_cb, and it means that a timer has expired
https://gerrit.osmocom.org/c/osmo-upf/+/28244/comment/7cb87127_da5b2dd2
PS3, Line 182: if (qe->m->is_response) {
> I see you are basically putting together in the same list 2 different things: […]
Let me rephrase your comment:
It would be more optimal to have separate lists for requests and responses.
You're right, thanks
--
To view, visit https://gerrit.osmocom.org/c/osmo-upf/+/28244
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-upf
Gerrit-Branch: master
Gerrit-Change-Id: Ic8d42e201b63064a71b40ca45a5a40e29941e8ac
Gerrit-Change-Number: 28244
Gerrit-PatchSet: 3
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: Thu, 09 Jun 2022 21:46:45 +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: pespin.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-upf/+/28245 )
Change subject: install libosmo-gtlv, libosmo-pfcp
......................................................................
Patch Set 3:
(1 comment)
Patchset:
PS1:
> We already discussed some of this and I think it was already agreed we definetly didn't want to move […]
Personally, I don't see a need to spend time on moving code between repositories.
I also think we have enough separate git repositories already.
I am still asking: what is the motivation for a separate repos?
It is effort, what is the reward? Why is it important to be discussed now?
libosmo-pfcp: comparing to libosmo-mgcp being part of osmo-mgw.git and osmo-stp being part of libosmo-sccp.git. Should those also move? IMHO it is fine in osmo-upf.git.
libosmo-tlv: it only makes sense to move it apart from libosmo-pfcp at the time when we start using it for something else than libosmo-pfcp. When that time comes I'd vote for libosmocore.git.
If the result of this discussion ends up to create libosmo-pfcp.git, I'd wait until after Harald's vacation.
--
To view, visit https://gerrit.osmocom.org/c/osmo-upf/+/28245
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-upf
Gerrit-Branch: master
Gerrit-Change-Id: I9f4651b6bee457583aba99052dc82bbf675515e6
Gerrit-Change-Number: 28245
Gerrit-PatchSet: 3
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: Thu, 09 Jun 2022 20:13:28 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: neels <nhofmeyr(a)sysmocom.de>
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment
pespin has uploaded a new patch set (#2). ( https://gerrit.osmocom.org/c/libosmocore/+/28258 )
Change subject: cbsp: Add enum and value string for Cause
......................................................................
cbsp: Add enum and value string for Cause
Change-Id: I35592bb4fff2e7b442d0e0cd537b66687862baf2
---
M TODO-RELEASE
M include/osmocom/gsm/cbsp.h
M src/gsm/cbsp.c
3 files changed, 47 insertions(+), 1 deletion(-)
git pull ssh://gerrit.osmocom.org:29418/libosmocore refs/changes/58/28258/2
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/28258
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: I35592bb4fff2e7b442d0e0cd537b66687862baf2
Gerrit-Change-Number: 28258
Gerrit-PatchSet: 2
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-CC: Jenkins Builder
Gerrit-MessageType: newpatchset
Attention is currently required from: osmith.
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-bsc/+/28257
to look at the new patch set (#2).
Change subject: src/osmo-bsc/bsc_vty.c: tweak msc pooling strings
......................................................................
src/osmo-bsc/bsc_vty.c: tweak msc pooling strings
Drop "to this MSC" from the NRI_STR, as it is not only used for MSC
specific configuration, but also in cfg_net_nri_* which affect all MSCs.
Drop "for this MSC" from the description of cfg_net_nri_null_del, it
affects all MSCs (unlike cfg_msc_nri_del).
Change-Id: Ic8888775a965b6d607af51b9359bd8ffc2834e16
---
M src/osmo-bsc/bsc_vty.c
M tests/nri_cfg.vty
2 files changed, 3 insertions(+), 3 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-bsc refs/changes/57/28257/2
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/28257
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: Ic8888775a965b6d607af51b9359bd8ffc2834e16
Gerrit-Change-Number: 28257
Gerrit-PatchSet: 2
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-MessageType: newpatchset
osmith has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-bsc/+/28257 )
Change subject: src/osmo-bsc/bsc_vty.c: tweak msc pooling strings
......................................................................
src/osmo-bsc/bsc_vty.c: tweak msc pooling strings
Drop "to this MSC" from the NRI_STR, as it is not only used for MSC
specific configuration, but also in cfg_net_nri_* which affect all MSCs.
Drop "for this MSC" from the description of cfg_net_nri_null_del, it
affects all MSCs (unlike cfg_msc_nri_del).
Change-Id: Ic8888775a965b6d607af51b9359bd8ffc2834e16
---
M src/osmo-bsc/bsc_vty.c
1 file changed, 2 insertions(+), 2 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-bsc refs/changes/57/28257/1
diff --git a/src/osmo-bsc/bsc_vty.c b/src/osmo-bsc/bsc_vty.c
index fc03c78..fb03d6f 100644
--- a/src/osmo-bsc/bsc_vty.c
+++ b/src/osmo-bsc/bsc_vty.c
@@ -1148,7 +1148,7 @@
return CMD_SUCCESS;
}
-#define NRI_STR "Mapping of Network Resource Indicators to this MSC, for MSC pooling\n"
+#define NRI_STR "Mapping of Network Resource Indicators, for MSC pooling\n"
#define NULL_NRI_STR "Define NULL-NRI values that cause re-assignment of an MS to a different MSC, for MSC pooling.\n"
#define NRI_FIRST_LAST_STR "First value of the NRI value range, should not surpass the configured 'nri bitlen'.\n" \
"Last value of the NRI value range, should not surpass the configured 'nri bitlen' and be larger than the" \
@@ -1195,7 +1195,7 @@
DEFUN_ATTR(cfg_net_nri_null_del,
cfg_net_nri_null_del_cmd,
"nri null del <0-32767> [<0-32767>]",
- NRI_STR NULL_NRI_STR "Remove NRI value or range from the NRI mapping for this MSC\n"
+ NRI_STR NULL_NRI_STR "Remove NRI value or range from the NRI mapping\n"
NRI_FIRST_LAST_STR,
CMD_ATTR_IMMEDIATE)
{
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/28257
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: Ic8888775a965b6d607af51b9359bd8ffc2834e16
Gerrit-Change-Number: 28257
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-MessageType: newchange
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/28253
to look at the new patch set (#2).
Change subject: hnodeb: Update primitives to audio SAPI version 1
......................................................................
hnodeb: Update primitives to audio SAPI version 1
Audio SAPI version 1 has been added recently in osmo-hnodeb.git
I860d18b80c1041bf63a1570d435e0568c0f6b01b.
Let's update our HNBLLIF emulation to support and use it.
Related: SYS#5516
Change-Id: I9af56f5e6a70b350f2fffa2e04be384d101b52ed
---
M hnodeb/HNBGW_ConnectionHandler.ttcn
M library/HNBLLIF_Templates.ttcn
M library/HNBLLIF_Types.ttcn
3 files changed, 19 insertions(+), 4 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/53/28253/2
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/28253
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: I9af56f5e6a70b350f2fffa2e04be384d101b52ed
Gerrit-Change-Number: 28253
Gerrit-PatchSet: 2
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-MessageType: newpatchset