Attention is currently required from: jolly, laforge.
pespin has posted comments on this change by jolly. ( https://gerrit.osmocom.org/c/libosmocore/+/40725?usp=email )
Change subject: Automatically increase io_uring, if too small.
......................................................................
Patch Set 9:
(6 comments)
Commit Message:
https://gerrit.osmocom.org/c/libosmocore/+/40725/comment/bf3fa1ff_1903038e?… :
PS9, Line 23: to determine when all submissions are completed.
Sounds like an easy thing to add right? It makes sense to implement this either her eor on a follow-up patch.
File src/core/osmo_io_internal.h:
https://gerrit.osmocom.org/c/libosmocore/+/40725/comment/b34815a0_ee55ba5c?… :
PS9, Line 110: bool read_enabled;
(At some point it may make sense to properly put all these fields into a "read" and "write" substructs in here.)
File src/core/osmo_io_uring.c:
https://gerrit.osmocom.org/c/libosmocore/+/40725/comment/09634797_688ca5a4?… :
PS9, Line 126: g_ring = talloc_zero(OTC_GLOBAL, struct osmo_io_uring);
are you sure OTC_GLOBAL is defined at this point? Or is it actually NULL?
If it's still NULL better pass NULL explicitly to avoid creating confusion.
https://gerrit.osmocom.org/c/libosmocore/+/40725/comment/afc5fac1_bb6d44e8?… :
PS9, Line 175: g_io_uring_size *= 2;
Once you move this to an unsigned, you can do "<< 1" here. BTW, I don't see you are making sure we don't go over the "maximum ring size allowed" in there, the one you are checking in previous commit.
https://gerrit.osmocom.org/c/libosmocore/+/40725/comment/6946c3e3_7a05083e?… :
PS9, Line 208: /* All subsequent read SQEs must be on the same ring. */
This should imho go inside iofd_uring_get_sqe(), based on "current_ring" being passed to it.
https://gerrit.osmocom.org/c/libosmocore/+/40725/comment/a8053e18_abe26da4?… :
PS9, Line 282: while (iofd->u.uring.reads_submitted < ((iofd->u.uring.num_read_sqes) ? : g_io_uring_read_sqes)) {
why is the g_io_uring_read_sqes reference needed here? How can iofd have num_read_sqes = 0, and if it does, why are we overriding it?
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/40725?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: Id9230146acc8d54bfd44834e783c31b37bd64bca
Gerrit-Change-Number: 40725
Gerrit-PatchSet: 9
Gerrit-Owner: jolly <andreas(a)eversberg.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: jolly <andreas(a)eversberg.eu>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Fri, 01 Aug 2025 11:46:46 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Attention is currently required from: jolly.
pespin has posted comments on this change by jolly. ( https://gerrit.osmocom.org/c/libosmocore/+/40782?usp=email )
Change subject: Add environment variable to set io_uring size
......................................................................
Patch Set 2: Code-Review+1
(3 comments)
File src/core/osmo_io_uring.c:
https://gerrit.osmocom.org/c/libosmocore/+/40782/comment/2136ce09_fe2b3fda?… :
PS2, Line 111: rc = osmo_str_to_int(&g_io_uring_size, env, 10, 1, 32768);
I wonder where 32768 comes from :D
https://gerrit.osmocom.org/c/libosmocore/+/40782/comment/360a1e2e_952260c3?… :
PS2, Line 116: if ((g_io_uring_size & (g_io_uring_size - 1))) {
if (g_io_uring_size & 0x01)
https://gerrit.osmocom.org/c/libosmocore/+/40782/comment/c8e2b206_2c594a91?… :
PS2, Line 117: fprintf(stderr, "Error: Initial io_uring size must be a positive power of two.\n");
Is this really needed as per io_uring API?
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/40782?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: I55289d9282e13aa1bf82f3931c85c196752f1484
Gerrit-Change-Number: 40782
Gerrit-PatchSet: 2
Gerrit-Owner: jolly <andreas(a)eversberg.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: jolly <andreas(a)eversberg.eu>
Gerrit-Comment-Date: Fri, 01 Aug 2025 11:23:34 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Attention is currently required from: fixeria.
pespin has posted comments on this change by fixeria. ( https://gerrit.osmocom.org/c/osmo-uecups/+/40806?usp=email )
Change subject: doc/examples: populate the config file example
......................................................................
Patch Set 1: Code-Review+2
--
To view, visit https://gerrit.osmocom.org/c/osmo-uecups/+/40806?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmo-uecups
Gerrit-Branch: master
Gerrit-Change-Id: I5c7b32903e2e205eb43b389292fe9bfceea36d30
Gerrit-Change-Number: 40806
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 01 Aug 2025 11:18:41 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: Yes
Attention is currently required from: laforge.
Hello Jenkins Builder, laforge,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/libosmocore/+/40725?usp=email
to look at the new patch set (#9).
The following approvals got outdated and were removed:
Verified+1 by Jenkins Builder
Change subject: Automatically increase io_uring, if too small.
......................................................................
Automatically increase io_uring, if too small.
The ring may be too small to store all SQEs before the kernel can
handle them. If this happens, a new ring is allocated with twice of the
size of the old ring. The old ring will not be destroyed, as it still
contains uncompleted elements. Some of them may never be completed.
A pointer to the current ring will be stored within the msghdr
structure. It is used when cancelling an SQE. The cancellation must be
performed in the same ring where it was created.
It is quite unlikely that the old ring cannot store the cancellation
SQE. If this happens, the cancellation is queued and submitted, once
the ring can store it.
The old ring will not be removed, because there is currently no counter
to determine when all submissions are completed.
Related: OS#6705
Change-Id: Id9230146acc8d54bfd44834e783c31b37bd64bca
---
M src/core/osmo_io_internal.h
M src/core/osmo_io_uring.c
2 files changed, 143 insertions(+), 39 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/libosmocore refs/changes/25/40725/9
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/40725?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newpatchset
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: Id9230146acc8d54bfd44834e783c31b37bd64bca
Gerrit-Change-Number: 40725
Gerrit-PatchSet: 9
Gerrit-Owner: jolly <andreas(a)eversberg.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Attention is currently required from: osmith.
Hello Jenkins Builder, osmith,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-ci/+/40804?usp=email
to look at the new patch set (#2).
The following approvals got outdated and were removed:
Verified+1 by Jenkins Builder
Change subject: jobs/gerrit-verifications: add logger_gsmtap
......................................................................
jobs/gerrit-verifications: add logger_gsmtap
Change-Id: I4ffae01156caa467ec23f6b89185b8d65d4691a3
Related: logger_gsmtap.git e06a0b9b3506e8ab1a7cfeeae72e32b2d6186989
---
M jobs/gerrit-verifications.yml
1 file changed, 6 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ci refs/changes/04/40804/2
--
To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/40804?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newpatchset
Gerrit-Project: osmo-ci
Gerrit-Branch: master
Gerrit-Change-Id: I4ffae01156caa467ec23f6b89185b8d65d4691a3
Gerrit-Change-Number: 40804
Gerrit-PatchSet: 2
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>