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/osmocom-commitlog@lists.osmocom.org/.
gitosis at osmocom.org gitosis at osmocom.orgThis 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 "UNNAMED PROJECT".
The branch, jerlbeck/flow-control has been updated
discards b218b819202556ed86cd1c428aee16fa778914ac (commit)
discards 68f7d29a5a4d7688a0e5737e7e6d94d72154e773 (commit)
discards 0f3882d233837bd74add250fc81aeeb5c9e71839 (commit)
via 6eeb7c7e74ed8cc1e23b19453012f43563055e12 (commit)
via 6e4ccec6c4b69681e94e4d3b27ef022e4aab81a9 (commit)
via 0288cdb0a8d4011905da55a5b74319e38e27e70d (commit)
via 3d62fc55d89fe1f2da0f0ca1950ab97da7e07418 (commit)
via 87d7341fbe290582ac4a03f67349496e5306eb04 (commit)
via 29d91e92715945f53aff4530602add765d63946e (commit)
This update added new revisions after undoing existing revisions. That is
to say, the old revision is not a strict subset of the new revision. This
situation occurs when you --force push a change and generate a repository
containing something like this:
* -- * -- B -- O -- O -- O (b218b819202556ed86cd1c428aee16fa778914ac)
\
N -- N -- N (6eeb7c7e74ed8cc1e23b19453012f43563055e12)
When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-pcu/commit/?id=6eeb7c7e74ed8cc1e23b19453012f43563055e12
commit 6eeb7c7e74ed8cc1e23b19453012f43563055e12
Author: Jacob Erlbeck <jerlbeck at sysmocom.de>
Date: Wed May 6 15:26:08 2015 +0200
bssgp: Increment BSSGP flow control tag value
Currently the tag value in FLOW CONTROL BVC messages is always 1.
This commit changes the implementation to increment that value with
each of the FLOW CONTROL BVC messages that is sent to the SGSN.
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/osmo-pcu/commit/?id=6e4ccec6c4b69681e94e4d3b27ef022e4aab81a9
commit 6e4ccec6c4b69681e94e4d3b27ef022e4aab81a9
Author: Jacob Erlbeck <jerlbeck at sysmocom.de>
Date: Wed May 6 14:24:36 2015 +0200
bssgp: Compute and transmit queue delay
The specification 28.018, allows to transmit the average LLC downlink
queueing delay in FLOW CONTROL BVC messages (BVC Measurement IE, see
GSM 28.018, 10.4.4 and 11.3.7).
This commit extends gprs_bssgp_pcu.cpp to compute the average delay
time between two subsequent FLOW CONTROL BVC messages. The average is
implemented as an arithmetic average without any weighting.
Ticket: OW#1432
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/osmo-pcu/commit/?id=0288cdb0a8d4011905da55a5b74319e38e27e70d
commit 0288cdb0a8d4011905da55a5b74319e38e27e70d
Author: Jacob Erlbeck <jerlbeck at sysmocom.de>
Date: Wed May 6 10:47:30 2015 +0200
bssgp: Add VTY command to Limit the bucket size by time
Currently the bucket size is by default being computed based on the
leak rate and the expected life time of LLC frames. The latter is
either taken from 'queue lifetime' (if given) or a fixed value is
used. Using 'queue lifetime' has the drawback that it sets a 'hard'
limit, since frames will be dropped if they stay in the queue
for a longer time.
This commit adds a VTY command to specifically set the time used for
the computation of the bucket size advertised to the SGSN. It does
not affect the PCUs queue handling in any way. If the bucket time is
not set (or if the 'no' command has been used), the old behaviour
(see above) is applied.
The following VTY commands are added (config-pcu node):
- flow-control bucket-time <1-65534> Sets the time in centisecs
- no flow-control bucket-time Don't use this time
Ticket: OW#1432
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/osmo-pcu/commit/?id=3d62fc55d89fe1f2da0f0ca1950ab97da7e07418
commit 3d62fc55d89fe1f2da0f0ca1950ab97da7e07418
Author: Jacob Erlbeck <jerlbeck at sysmocom.de>
Date: Thu Apr 30 15:01:15 2015 +0200
bssgp: Compute BVC bucket size and leak rate
Currently the PDCH assignment and coding scheme does not influence
the values transmitted by the FLOW-CONTROL-BVC messages.
This commit adds the computation of those values. If the leak rate is
not given explicitly, it is derived from the number of PDCH and the
allowed coding scheme. If the BVC bucket size is not given
explicitly, it is derived from the leak rate and the maximum buffer time.
The latter is taken from the 'queue lifetime' command (or 10s if this
has not been used). The MS default bucket size is set to 50% of the
BVC bucket size. The MS default rate computation assumes, that each MS
only supports up to 4 time slots for GPRS RX.
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/osmo-pcu/commit/?id=87d7341fbe290582ac4a03f67349496e5306eb04
commit 87d7341fbe290582ac4a03f67349496e5306eb04
Author: Jacob Erlbeck <jerlbeck at sysmocom.de>
Date: Tue Apr 21 12:56:48 2015 +0200
bssgp: Make BVC bucket size / leak rate configurable
Currently the FLOW-CONTROL_BVC message contains fixed values: The tag
is 1, the BVC bucket size is 6MB, the BVC bucket leak rate is
820kbit/s, the MS bucket size is 50kB, and the MS leak rate is
50kbit/s.
This commit makes the BVC parameters configurable and adds the
following VTY commands:
- flow-control force-bvc-bucket-size <1-6553500>
- no flow-control force-bvc-bucket-size
- flow-control force-bvc-leak-rate <1-6553500>
- no flow-control force-bvc-leak-rate
- flow-control force-ms-bucket-size <1-6553500>
- no flow-control force-ms-bucket-size
- flow-control force-ms-leak-rate <1-6553500>
- no flow-control force-ms-leak-rate
The 'no' variants restore the default behaviour.
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/osmo-pcu/commit/?id=29d91e92715945f53aff4530602add765d63946e
commit 29d91e92715945f53aff4530602add765d63946e
Author: Jacob Erlbeck <jerlbeck at sysmocom.de>
Date: Wed Apr 29 14:46:52 2015 +0200
tbf: Added calls to llc_dropped_frame
Currently this function which increments the corresponding counter is
just called in gprs_llc::clear(). It is not called on places where
LLC DISCARDED messages are sent.
This commit adds calls to llc_dropped_frame() at these places.
Sponsored-by: On-Waves ehf
-----------------------------------------------------------------------
Summary of changes:
src/bts.h | 1 +
src/gprs_bssgp_pcu.cpp | 162 +++++++++++++++++++++++++++++++++++++------------
src/gprs_bssgp_pcu.h | 8 +++
src/pcu_vty.c | 28 +++++++++
src/tbf_dl.cpp | 16 +++--
5 files changed, 171 insertions(+), 44 deletions(-)
hooks/post-receive
--
UNNAMED PROJECT