From: gitosis@osmocom.org Precedence: list To: osmocom-commitlog@lists.osmocom.org Date: Thu, 20 Jun 2013 11:58:19 GMT Message-ID: <201306201158.r5KBwJlZ075311@git.osmocom.org> Subject: osmo-bts.git branch sysmocom/0.3.0-next created. 0.3.0-5-gd7b37b6 Message: 4 This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Osmocom BTS-side code (Abis, scheduling, ...)". The branch, sysmocom/0.3.0-next has been created at d7b37b68cacc508fb2814013bfdbee081cd29efd (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-bts/commit/?id=d7b37b68cacc508fb2814013bfdbee081cd29efd commit d7b37b68cacc508fb2814013bfdbee081cd29efd Author: Holger Hans Peter Freyther Date: Wed May 1 16:52:27 2013 +0200 sysmobts: Make sure we receive every SACCH frame to count S properly In case there is no transmitter the S counter might never be decreased. This means that no radio link timeout will not be sent and the lchan will remain open forever. There are several ways to resolve this. The first would be to use the MphTimeInd and after each multiframe check if there has been a SACCH message for the open lchan's. This could be similar to the trx_meas_check_compute. I decided to change fBFILevel to always receive SACCH frames and move the code down to the PDTCH/PACCH handling and update the comment. http://cgit.osmocom.org/osmo-bts/commit/?id=ad578e571389c0e07834f25880f569cf708a705c commit ad578e571389c0e07834f25880f569cf708a705c Author: Holger Hans Peter Freyther Date: Wed May 1 16:13:37 2013 +0200 sysmobts: Read multiple primitives at once but only up to 3 In most cases there are multiple messages ready to be read from the queue and it is more efficient to read them in one go instead of going through the select again. http://cgit.osmocom.org/osmo-bts/commit/?id=603cc316572ede1e7d30cc24cb5ac3cf5438b36a commit 603cc316572ede1e7d30cc24cb5ac3cf5438b36a Author: Holger Hans Peter Freyther Date: Sat May 4 11:30:18 2013 +0200 sysmobts: Use writev for the outgoing data of the write queue Attempt to write multiple primitives at the same time instead of the select/write, select/write that is currently done. The queue size is big enough to hold several entries at the same time and it is unlikely we get the -EAGAIN from the kernel driver. The writev code works by assuming that each element in the queue has the same size. This is not verified by the code and if this assumption breaks at some point the code will drop primitives or send some twice. http://cgit.osmocom.org/osmo-bts/commit/?id=c905ba18516f371de52e1b1af26acbe044ab1e7c commit c905ba18516f371de52e1b1af26acbe044ab1e7c Author: Holger Hans Peter Freyther Date: Wed May 1 08:51:17 2013 +0200 sysmobts: Fix potential memory leaks in the prim callback handling Make sure the l1msg is always freed in the callback. There were several error conditions were the msgb would not have been freed, in the case of the calib data and the system information the message was not freed even in normal condition. I will modify this code to __use a msgb. This allows to re-use the allocated msgb across read operations. http://cgit.osmocom.org/osmo-bts/commit/?id=66c85bdc46c8167e7b1a80d46d24262b5dd2d621 commit 66c85bdc46c8167e7b1a80d46d24262b5dd2d621 Author: Holger Hans Peter Freyther Date: Wed May 8 18:25:02 2013 +0200 leak: Fix a +ptrsize memory leak for each opened lchan The lapdm/lapd_core code needs to keep a history of messages sent. This history is not freed when lapdm_channel_reset is called and the init code will just allocate a new array. This means there is a memory leak on every released channel every time it is released. ----------------------------------------------------------------------- hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)