Osmo io » History » Version 1
laforge, 03/13/2024 08:33 AM
1 | 1 | laforge | h1. osmo_io |
---|---|---|---|
2 | |||
3 | @osmo_io@ is the new way of ho we do I/O in osmocom projects. It moves from a raw select/poll abstraction (where every application performs its own read/write once the fd becomes readble/writable) to a submission/completion model, where the actual I/O is performed by the library, an the application just submits write requests (as @struct msgb@) and receives write-completion and read-completion call-backs. |
||
4 | |||
5 | For more information, see: FIXME |
||
6 | |||
7 | h2. Implementation status |
||
8 | |||
9 | The below table indicates the implementation status of the osmo_io migration: |
||
10 | |||
11 | |_.library/interface|_.protocol|_.transport|_.users|_.commit| |
||
12 | |libosmo-mgcp-client|MGCP|UDP|osmo-bsc, osmo-msc, osmo-hnbgw|"osmo-mgw":https://gitea.osmocom.org/cellular-infrastructure/osmo-mgw/commit/8b524c9151177d681b35332146d7628fafd82846| |
||
13 | |libosmogb ns2|NS|UDP|osmo-pcu, osmo-gbproxy, osmo-sgsn|"libosmocore":https://gitea.osmocom.org/osmocom/libosmocore/commit/eb9edbab54463cb705ec7b770e022a215ce503c7| |
||
14 | |osmo-bsc|CBSP|TCP client+server|osmo-bsc|"osmo-bsc":https://gitea.osmocom.org/cellular-infrastructure/osmo-bsc/commit/85687bf176e4b9663f2396a27c28b49221c72fa3| |
||
15 | |osmo-bsc|meas_feed|UDP|osmo-bsc|"osmo-bsc":https://gitea.osmocom.org/cellular-infrastructure/osmo-bsc/commit/ea388e1db1465afdcfd2796336732d29d80a2b9f| |
||
16 | |libosmo-netif|stream_cli|TCP|libosmo-sigtran(ipa), osmo-bsc(cbsp), osmo-cbc(cbsp)|"libosmo-netif":https://gitea.osmocom.org/osmocom/libosmo-netif/commit/0e7028f742dedefd9fccc2d5b26875fca4036f58| |
||
17 | |libosmo-netif|stream_cli|SCTP|libosmo-sigtran|"libosmo-netif":https://gitea.osmocom.org/osmocom/libosmo-netif/commit/7e6d2e0f99ff095f4714f03b1ed991d6c9cb9c61| |
||
18 | |libosmo-sigtran|xUA ASP (SUA, M3UA)|SCTP|osmo-bsc, osmo-msc, osmo-sgsn, osmo-hnbgw|TBD| |