diff options
author | Dimitri Staessens <[email protected]> | 2022-03-28 20:08:12 +0200 |
---|---|---|
committer | Sander Vrijders <[email protected]> | 2022-03-30 15:12:25 +0200 |
commit | efe850f4f90967649cdb27cfa29ca0a17127f932 (patch) | |
tree | 38306f31b9c0c950788ea23e0639365c10067e5f /src/tools/operf/operf.c | |
parent | 1330cf5d2491897bbdfafe09f743599fe4ea97ea (diff) | |
download | ouroboros-efe850f4f90967649cdb27cfa29ca0a17127f932.tar.gz ouroboros-efe850f4f90967649cdb27cfa29ca0a17127f932.zip |
lib: Move incoming FRCT handling to own thread
The application will now handle incoming FRCT packets even if the
application never reads data from the flow (for instance servers). To
do this, it reserves an fset_t (id 0). When an FRCT-enabled flow is
created, it is automatically added to this fset. An rx thread will
listen for incoming events and perform necessary actions on the flow
if needed. If the FRCT flow is added to another user fset, it will be
handled by that user fset (and if the flow is removed from a user
fset, it will be re-added to the set with id 0 to be handled by the
rx_flow thread. The flow monitoring is handled by the same thread,
replacing the previous monitoring thread.
Signed-off-by: Dimitri Staessens <[email protected]>
Signed-off-by: Sander Vrijders <[email protected]>
Diffstat (limited to 'src/tools/operf/operf.c')
0 files changed, 0 insertions, 0 deletions