Actions
Feature #6389
openport VTY over to osmo_io / io_uring
Status:
New
Priority:
Low
Assignee:
-
Category:
libosmovty
Target version:
-
Start date:
03/02/2024
Due date:
% Done:
0%
Spec Reference:
Description
The VTY uses its 'buffer' layer between writes by the software and writing to the acutal socket file descriptor. buffer_flush_all is currently used whenever the socket is write-able. So it's a pull model.
We'd probably have to change that logic to work the other way around: Once a buffer has a certain fill-level (or age?), proactively push it via osmo_io.
Unless somebody uses a lot of scripts acccessing the VTY, it's also unlikely that the syscall load of a human VTY user would place significant I/O load on an osmocom program. So it's not super criticial.
Related issues
Actions