Feature #1884
closed
distribute measurement processing accross timeslots
Added by laforge over 7 years ago.
Updated over 6 years ago.
Description
right now, we call
It might be an idea to simply trigger lchan_meas_check_compute() after processing of each PH-DATA.ind primitive. The rationale would be:
- there can be no new measurment information without a new PH-DATA.ind
- rather than iterating over all TS and all lchan inside the TS at every TS=0, we can ddistribute the CPU load accross the entire FRAME, reducing any special processing happening at TS=0 when MPH-DATA.ind is received.
- Related to Bug #1883: RACH load computation is wrong added
- Assignee changed from laforge to dexter
I think this is alrady implemented? please keep the tickets up to date at least once per week (ticket review monday!).
laforge wrote:
I think this is alrady implemented? please keep the tickets up to date at least once per week (ticket review monday!).
ping? Please don't make me remind you to reminders of keeping tickets up to date. thanks!
- Status changed from New to In Progress
The current callgraph is: l1sap_up() -> l1sap_mph_info_ind() -> l1sap_info_meas_ind() -> lchan_meas_check_compute()
l1sap_mph_info_ind() is called when PRIM_MPH_INFO is received. When the type is PRIM_INFO_MEAS l1sap_info_meas_ind() called.
I am not sure if that is what is required by the ticket. Above it says that lchan_meas_check_compute() should be called on every MPH-DATA.ind (or do you mean PH-DATA.ind? / PRIM_PH_DATA).
- Status changed from In Progress to Stalled
- Status changed from Stalled to Feedback
- Status changed from Feedback to Closed
Meta Information: If you want feedback, you need to assign the ticket to whom you are expecting feedback from. Otherwise the person (in this case me) has no way of knowing he has something to do in the ticket)
Also available in: Atom
PDF
