osmo-pcu.git branch jerlbeck/flow-control updated. 0.2-408-g01e7c1f

gitosis at osmocom.org gitosis at osmocom.org
Thu Apr 30 17:53:25 UTC 2015

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 "UNNAMED PROJECT".

The branch, jerlbeck/flow-control has been updated
  discards  b9b0321428fa29dbb72c308901ce3df1adcb8d55 (commit)
       via  01e7c1f338144df3685290daf24d0c0d43f57176 (commit)
       via  ace99d5f853ae3371d71ee53c40b44877cf8c500 (commit)
       via  cd16e40e1afe34201aab77e09567c7ab5be9392e (commit)
       via  68c1495a820d6e20b8df8d77445cec4b9018104a (commit)
       via  fcb8e6560c5e12f55518479c6fd22344d233e9cb (commit)
       via  56e8d710907b9320d41a6285f08bba39aae2ee3b (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 (b9b0321428fa29dbb72c308901ce3df1adcb8d55)
             N -- N -- N (01e7c1f338144df3685290daf24d0c0d43f57176)

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 -----------------------------------------------------------------

commit 01e7c1f338144df3685290daf24d0c0d43f57176
Author: Jacob Erlbeck <jerlbeck at sysmocom.de>
Date:   Thu Apr 30 17:55:16 2015 +0200

    vty: Fix value range of commands accepting csecs
    Currently an uint8_t csec variable is used to temporarily store
    the number of centiseconds which can be set within the range
    1 - 65535. This way values above 255 cannot be set properly. This
    affects the VTY commands "queue lifetime", "queue hysteres", and
    "queue idle-ack-delay".
    This commit replaces the uint8_t by an uint16_t.
    Sponsored-by: On-Waves ehf


commit ace99d5f853ae3371d71ee53c40b44877cf8c500
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 25% of the
    BVC bucket size.


commit cd16e40e1afe34201aab77e09567c7ab5be9392e
Author: Jacob Erlbeck <jerlbeck at sysmocom.de>
Date:   Thu Apr 30 15:59:01 2015 +0200

    vty: Fix warnings about undeclared functions
    This commit adds missing includes to pcu_vty.c and fixes the
    llist_head type (missing struct keyword) used by tbf_print_vty_info.
    Sponsored-by: On-Waves ehf


commit 68c1495a820d6e20b8df8d77445cec4b9018104a
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
    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


commit fcb8e6560c5e12f55518479c6fd22344d233e9cb
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


commit 56e8d710907b9320d41a6285f08bba39aae2ee3b
Author: Jacob Erlbeck <jerlbeck at sysmocom.de>
Date:   Mon Apr 27 16:28:58 2015 +0200

    tbf: Remove double assigment to m_last_dl_drained_fn
    Currently the value -1 is assigned twice to m_last_dl_drained_fn
    within append_data().
    This commit removes the first of these assigments.
    Sponsored-by: On-Waves ehf


Summary of changes:
 src/bts.h              |   2 +
 src/gprs_bssgp_pcu.cpp |  90 +++++++++++++++++++++++++++++++++++++--
 src/pcu_main.cpp       |   2 -
 src/pcu_vty.c          | 113 ++++++++++++++++++++++++++++++++++++++++++++-----
 src/tbf.cpp            |   2 +-
 src/tbf.h              |   3 +-
 src/tbf_dl.cpp         |   4 +-
 7 files changed, 196 insertions(+), 20 deletions(-)


More information about the osmocom-commitlog mailing list