hotfix: RLC AM reported wrong number of bytes to retransmit

This was causing oaisim to fail way too often at the startup
of a connection.

Things should go better with this patch.

It may not be the end of the story, the use of retrans_num_bytes_to_retransmit
is not clear to me. The problem I see is: what if the max number of
retransimission has been reached (if that has a meaning at all in RLC AM)?
will this value be decreased or not?
This commit is contained in:
Cedric Roux
2016-07-20 17:54:21 +02:00
parent d0b046581c
commit 833714406c
+1 -1
View File
@@ -103,7 +103,7 @@ rlc_am_get_buffer_occupancy_in_bytes (
} }
#endif #endif
return rlc_pP->status_buffer_occupancy + rlc_pP->retransmission_buffer_occupancy + rlc_pP->sdu_buffer_occupancy + max_li_overhead + header_overhead; return rlc_pP->status_buffer_occupancy + rlc_pP->retrans_num_bytes_to_retransmit + rlc_pP->sdu_buffer_occupancy + max_li_overhead + header_overhead;
} }
//----------------------------------------------------------------------------- //-----------------------------------------------------------------------------
void void