Attention is currently required from: kirr, pespin.

kirr uploaded patch set #2 to this change.

View Change

The following approvals got outdated and were removed: Code-Review+1 by pespin, Verified+1 by Jenkins Builder

trx_toolkit/*: Try to avoid copying burst data where possible

Conveying burst data is the primary flow in data place of what fake_trx
does, so the less copies we do, the less we make CPU loaded.

After this change I can finally run 1 BTS + 2 Mobile + 1 ccch_scan
without hitting "Stale message ..." on fake_trx side. However fake_trx
cpu load is close to 100% and there are internal clock overruns often:

    [WARNING] clck_gen.py:97 CLCKGen: time overrun by -1385us; resetting the clock
    [WARNING] clck_gen.py:97 CLCKGen: time overrun by -2657us; resetting the clock
    [WARNING] clck_gen.py:97 CLCKGen: time overrun by -1264us; resetting the clock
    [WARNING] clck_gen.py:97 CLCKGen: time overrun by -2913us; resetting the clock
    [WARNING] clck_gen.py:97 CLCKGen: time overrun by -1836us; resetting the clock
    ...

This suggests that even though fake_trx.py + tx-queue started to work
somehow, the rewrite of fake_trx in C, as explained in OS#6672, is still
better to do.

Change-Id: I147da2f110dedc863361059c931f609c28a69e9c
---
M src/target/trx_toolkit/data_if.py
M src/target/trx_toolkit/data_msg.py
2 files changed, 27 insertions(+), 37 deletions(-)

git pull ssh://gerrit.osmocom.org:29418/osmocom-bb refs/changes/37/39537/2

To view, visit change 39537. To unsubscribe, or for help writing mail filters, visit settings.