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/wip/ms-struct has been updated
discards 35558a89aa5d3f8eb8c805d2c8412f409e090b88 (commit)
discards e4947f1bb86a251dce68cb695d9fca16adff6bf4 (commit)
discards 89cde650e249e9791455a3752caa5af2f2923ce8 (commit)
via 20296a48676094a09c7928006e62e890c2e69e0f (commit)
via 87e6ed022df45b70d93c96581cc1c99b76a80718 (commit)
via 6e3311b641b51cb4cc790f2e488e45602724ce36 (commit)
via 7044acabf5ac371a4e80bb1fc81650b36187deaa (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 (35558a89aa5d3f8eb8c805d2c8412f409e090b88)
\
N -- N -- N (20296a48676094a09c7928006e62e890c2e69e0f)
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=20296a48676094a09c7928006e62e89…
commit 20296a48676094a09c7928006e62e890c2e69e0f
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Fri May 22 18:02:51 2015 +0200
tbf: Remove TimingAdvance storage
Currently the TA storage stores up to 30 TLLI->TA mappings, if more
entries are created the oldest one is dropped. In theory this can
lead to missing TA information if many MS are present.
This commit removes the TimingAdvance class completely, since the TA
value is now stored in the GprsMs objects.
Note that the GprsMs objects are currently not kept after the TBFs
have detached from them, so the TA values are now kept for a shorter
time than before.
Ticket: #1674
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/osmo-pcu/commit/?id=87e6ed022df45b70d93c96581cc1c99…
commit 87e6ed022df45b70d93c96581cc1c99b76a80718
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Fri May 22 17:48:04 2015 +0200
tbf: Store the timing advance (TA) value in the GprsMs object
The TA value rather relates to an MS and not to a single TBF. So all
TBFs share the same TA value. Currently the TA value is stored per
TBF and eventually copied from an old TBF to a new one. It is in
general only passed with an RACH request when the TLLI and thus the
MS is not yet known.
This commit adds a TA member to the GprsMs class and uses that one
when the TBF is associated to an MS object. Since the TBF is not
always associated with an MS object (after RACH or when it has been
replaced by another TBF), the TA value is still stored in each TBF
and that value is used as long as no MS object is being associated.
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/osmo-pcu/commit/?id=6e3311b641b51cb4cc790f2e488e456…
commit 6e3311b641b51cb4cc790f2e488e45602724ce36
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Wed May 27 13:03:15 2015 +0200
tbf/test: Add tests for single and two phase access
These tests cover the message exchange from receiving from the first
RACH request to the first data block when establishing an uplink TBF.
This will be used to check, whether TA and other values are passed to
an MS object correctly.
In addition, the RX RACH log message in rcv_rach is extended to
contain the single block fn.
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/osmo-pcu/commit/?id=7044acabf5ac371a4e80bb1fc81650b…
commit 7044acabf5ac371a4e80bb1fc81650b36187deaa
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Fri May 22 15:47:55 2015 +0200
tbf: Remove TBF chaining (m_new_tbf and m_old_tbf)
Currently a new TBF is chained to an existing older one, either of
the other direction (active or releasing) or of the same direction
(releasing). This does not work properly work if and uplink and a
downlink TBF are being established at the same time while an old TBF
is being released. In that case, one of them is thrown away and the
pending procedure is cancelled.
The chaining is no longer necessary since the GprsMs objects have
been introduced which keep track of the active TBFs.
This commit removes the TBF members m_new_tbf and m_old_tbf and the
related methods and code paths.
Note that a new TBF can replace an older TBF entry of the same
direction within an MS object when it is associated with an MS (e.g.
by TLLI or because it is assigned via another, already associated
TBF). In that case, the old TBF is no longer associated with an MS
object.
Ticket: #1674
Sponsored-by: On-Waves ehf
-----------------------------------------------------------------------
Summary of changes:
src/bts.cpp | 7 +--
src/tbf.cpp | 3 ++
tests/tbf/TbfTest.cpp | 144 ++++++++++++++++++++++++++++++++++++++++++++++++++
tests/tbf/TbfTest.err | 98 ++++++++++++++++++++++++++++++++++
tests/tbf/TbfTest.ok | 4 ++
5 files changed, 253 insertions(+), 3 deletions(-)
hooks/post-receive
--
UNNAMED PROJECT