[PATCH] Release lchan directly when refcount drops to zero

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Harald Welte laforge at gnumonks.org
Fri Nov 20 13:04:35 UTC 2009


Hi zecke,

On Wed, Nov 18, 2009 at 10:19:27AM +0100, Holger Freyther wrote:
> Hi all,
> 
> I have written this small patch yesterday. It is removing the "auto release" 
> after timeout from lchan and will directly release the channel ones the ref 
> count drops to zero.

thanks for investigating this.

The reason why we have this long timeout is mainly due to MO SMS.

What happens in the MO SMS case is that we get a CM SERVICE REQUEST is that the
channel stays active for a very long time (especially if you have a very long
sms) before we get the actual CP-DATA.

If our timeout is too low, then the channel will simply timeout while the SMS
is being transmitted.

So what do we do here in order to solve the issue ? Handle CM SERVICE REQUEST
as a special case and manually increase it or start some special timer?

The only idea I had was that we should be getting and ESTABLISH INDICATION on
SAPI=3, but I'm not sure if that happens before the CP-DATA.

So whatever change you make, if it survives sending a maximum-sized MO SMS ona
SDCCH (plus even accounting for some L2 retransmissions), then I'm happy with
it!

Regards,
	Harald

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)




More information about the OpenBSC mailing list