Attention is currently required from: fixeria.

laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/31672 )

Change subject: osmo-bts-trx: alloc/free burst buffers in trx_sched_set_lchan() ......................................................................

Patch Set 4:

(1 comment)

Commit Message:

https://gerrit.osmocom.org/c/osmo-bts/+/31672/comment/0b23a505_f9d1cc05 PS4, Line 14: o that we can dynamically choose : buffer size depending on the channel mode (speech/data). I don't know if this is really an advantage. Sounds to me like we just put more load on the memory allocator and cause more memory fragmentation.

There's nothing wrong with a TRX allocating the maximum buffer size for all the burst buffers it needs in the "worst case" scenario once at start-up, and then using them as needed.

It's not like the total size of all those burst buffers is ever going to be of concern on any of our target platforms, right?

It's not super critical, after all we're not activating/deactivating hundreds or thousands of timeslots per second. But still something to think about.