diff options
author | Erik Hugne <erik.hugne@ericsson.com> | 2012-11-07 02:40:07 -0500 |
---|---|---|
committer | Paul Gortmaker <paul.gortmaker@windriver.com> | 2012-12-06 17:20:19 -0500 |
commit | c008413850d1d48cc02c940280bf2dcf76160f4c (patch) | |
tree | d24c2056bfe41060d214c0b44344d366b655e9a9 /arch/h8300/boot | |
parent | b93196dc5af7729ff7cc50d3d322ab1a364aa14f (diff) | |
download | linux-3.10-c008413850d1d48cc02c940280bf2dcf76160f4c.tar.gz linux-3.10-c008413850d1d48cc02c940280bf2dcf76160f4c.tar.bz2 linux-3.10-c008413850d1d48cc02c940280bf2dcf76160f4c.zip |
tipc: remove obsolete flush of stale reassembly buffer
Each link instance has a periodic job checking if there is a stale
ongoing message reassembly associated to the link. If no new
fragment has been received during the last 4*[link_tolerance] period,
it is assumed the missing fragment will never arrive. As a consequence,
the reassembly buffer is discarded, and a gap in the message sequence
occurs.
This assumption is wrong. After we abandoned our ambition to develop
packet routing for multi-cluster networks, only single-hop packet
transfer remains as an option. For those, all packets are guaranteed
to be delivered in sequence to the defragmentation layer. Any failure
to achieve sequenced delivery will eventually lead to link reset, and
the reassembly buffer will be flushed anyway.
So we just remove this periodic check, which is now obsolete.
Signed-off-by: Erik Hugne <erik.hugne@ericsson.com>
Acked-by: Ying Xue <ying.xue@windriver.com>
Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
[PG: also delete get/inc_timer count, since they are now unused]
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Diffstat (limited to 'arch/h8300/boot')
0 files changed, 0 insertions, 0 deletions