Project

General

Profile

Actions

Feature #5753

closed

io_uring support in libosmo-netif

Added by laforge over 1 year ago. Updated 16 days ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
11/09/2022
Due date:
% Done:

100%

Spec Reference:
Tags:

Description

Once libosmocore provides the new API for the upcoming io_uring backend (#5751) we will need to port libosmo-netif over to this new API.

Currently we're using the following code-paths for I/O

libosmo-netif function I/O function provided by
osmo_stream_{cli,srv}_recv recv -
osmo_stream_srv_recv sctp_recvmsg libsctp
osmo_stream_cli_write send -
osmo_stream_{cli,srv}_write sctp_send libsctp

We need to analyze each of those and migrate, if possible.


Files

chatlog.txt chatlog.txt 9.44 KB arehbein, 07/02/2023 05:21 PM

Related issues

Related to libosmocore - Feature #5751: io_uring support in libosmocoreIn Progressjolly11/09/2022

Actions
Related to libosmo-sccp + libosmo-sigtran - Feature #5752: io_uring support in libosmo-sigtranResolvedjolly11/09/2022

Actions
Related to libosmo-netif - Bug #6164: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]Resolvedarehbein08/31/2023

Actions
Related to libosmo-netif - Bug #6279: stream_cli fails to connect when using SCTP if no local address is setResolvedlaforge11/29/2023

Actions
Related to Core testing infrastructure - Feature #6357: run (some?) tests with io_uring backend for osmo_ioNewosmith02/09/2024

Actions
Blocked by libosmo-netif - Bug #6222: Memory leak triggered by stream_testResolvedarehbein10/17/2023

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)