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 01e7c1f338144df3685290daf24d0c0d43f57176 (commit) discards ace99d5f853ae3371d71ee53c40b44877cf8c500 (commit) discards cd16e40e1afe34201aab77e09567c7ab5be9392e (commit) discards 68c1495a820d6e20b8df8d77445cec4b9018104a (commit) via 5e1a8403564b2af351ad8a8d462488cc25648dd8 (commit) via fe865b1887d58302e7a68b6b01b5de69f35b0870 (commit) via 47e945161b06edf51f19ec4d7b7baec1f09ce8b8 (commit) via bcfa2f67b4b19174964d64992f34fae12adbcc84 (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 (01e7c1f338144df3685290daf24d0c0d43f57176) \ N -- N -- N (5e1a8403564b2af351ad8a8d462488cc25648dd8) 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=5e1a8403564b2af351ad8a8d462488c… commit 5e1a8403564b2af351ad8a8d462488cc25648dd8 Author: Jacob Erlbeck &lt;jerlbeck(a)sysmocom.de&gt; 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 http://cgit.osmocom.org/osmo-pcu/commit/?id=fe865b1887d58302e7a68b6b01b5de6… commit fe865b1887d58302e7a68b6b01b5de69f35b0870 Author: Jacob Erlbeck &lt;jerlbeck(a)sysmocom.de&gt; 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=47e945161b06edf51f19ec4d7b7baec… commit 47e945161b06edf51f19ec4d7b7baec1f09ce8b8 Author: Jacob Erlbeck &lt;jerlbeck(a)sysmocom.de&gt; 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 http://cgit.osmocom.org/osmo-pcu/commit/?id=bcfa2f67b4b19174964d64992f34fae… commit bcfa2f67b4b19174964d64992f34fae12adbcc84 Author: Jacob Erlbeck &lt;jerlbeck(a)sysmocom.de&gt; 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 ----------------------------------------------------------------------- Summary of changes: src/pcu_vty.c | 1 - 1 file changed, 1 deletion(-) hooks/post-receive -- UNNAMED PROJECT