lib: Move timerwheel processing to its own thread

This is the first step moving away from scheduling the FRCT and flow
monitoring functions as part of the IPC calls (flow_read / flow_write
/ fevent) and towards the more scalable (and far less complicated)
implementation to take care of these functions in separate threads.

If a process creates the first flow that requires FRCT, it will spin
up a thread to process events on the timerwheel (retransmissions and
delayed ACKs). This single thread lives until the last flow with FRCT
is deallocated.

Signed-off-by: Dimitri Staessens <[email protected]>
Signed-off-by: Sander Vrijders <[email protected]>

1 files changed, 0 insertions, 8 deletions

diff --git a/src/lib/frct.c b/src/lib/frct.c
index a93a1006..2d31e6f2 100644
--- a/src/lib/frct.c
+++ b/src/lib/frct.c
@@ -467,9 +467,6 @@ static void frcti_setflags(struct frcti * frcti,
 #define frcti_rcv(frcti, sdb)                           \
         (frcti == NULL ? 0 : __frcti_rcv(frcti, sdb))
 
-#define frcti_tick(frcti)                               \
-        (frcti == NULL ? 0 : __frcti_tick())
-
 #define frcti_dealloc(frcti)                            \
         (frcti == NULL ? 0 : __frcti_dealloc(frcti))
 
@@ -769,11 +766,6 @@ static void rtt_estimator(struct frcti * frcti,
         frcti->rto      = MAX(RTO_MIN, frcti->srtt + (frcti->mdev << 2));
 }
 
-static void __frcti_tick(void)
-{
-        timerwheel_move();
-}
-
 /* Always queues the next application packet on the RQ. */
 static void __frcti_rcv(struct frcti *       frcti,
                         struct shm_du_buff * sdb)