osmo-pcu.git branch jerlbeck/flow-control updated. 0.2-412-gb218b81

gitosis at osmocom.org gitosis at osmocom.org
Tue May 5 07:44: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  5e1a8403564b2af351ad8a8d462488cc25648dd8 (commit)
  discards  fe865b1887d58302e7a68b6b01b5de69f35b0870 (commit)
  discards  47e945161b06edf51f19ec4d7b7baec1f09ce8b8 (commit)
  discards  bcfa2f67b4b19174964d64992f34fae12adbcc84 (commit)
  discards  fcb8e6560c5e12f55518479c6fd22344d233e9cb (commit)
       via  b218b819202556ed86cd1c428aee16fa778914ac (commit)
       via  68f7d29a5a4d7688a0e5737e7e6d94d72154e773 (commit)
       via  0f3882d233837bd74add250fc81aeeb5c9e71839 (commit)
       via  801d6fe40cd5bd11257074c7aaf113a57919fb2d (commit)
       via  0494c75a53f05a5ec4c4b3830672ef2451396f27 (commit)
       via  0d39dc92b5cfe6e8be9b2a68eaf50c94cae97355 (commit)
       via  1f33294b1c1394c6ff0dd109ff10bb65886c1a44 (commit)
       via  2acfbebfd3b7fc24ccaf2115e7c8d55e94cd1450 (commit)
       via  c0c580c414e4fe0bd82ebc78ff12bb1014cd5a9c (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 (5e1a8403564b2af351ad8a8d462488cc25648dd8)
            \
             N -- N -- N (b218b819202556ed86cd1c428aee16fa778914ac)

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

commit b218b819202556ed86cd1c428aee16fa778914ac
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.

http://cgit.osmocom.org/osmo-pcu/commit/?id=68f7d29a5a4d7688a0e5737e7e6d94d72154e773

commit 68f7d29a5a4d7688a0e5737e7e6d94d72154e773
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=0f3882d233837bd74add250fc81aeeb5c9e71839

commit 0f3882d233837bd74add250fc81aeeb5c9e71839
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.cpp                           |  2 +-
 src/sysmo_l1_if.h                     | 10 ++++++++++
 tests/alloc/AllocTest.cpp             | 16 +++++++---------
 tests/emu/pcu_emu.cpp                 |  6 +++---
 tests/emu/test_pdp_activation.cpp     |  4 +---
 tests/emu/test_replay_gprs_attach.cpp |  2 +-
 tests/tbf/TbfTest.cpp                 |  2 +-
 tests/types/TypesTest.cpp             |  2 --
 8 files changed, 24 insertions(+), 20 deletions(-)


hooks/post-receive
-- 
UNNAMED PROJECT



More information about the osmocom-commitlog mailing list