diff options
author | Jon Paul Maloy <jon.maloy@ericsson.com> | 2014-02-13 17:29:16 -0500 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2014-02-13 17:57:07 -0500 |
commit | 7d33939f475d403e79124e3143d7951dcfe8629f (patch) | |
tree | ebc054f8e172f038efd53cd977e78eb1ac3f78e6 /mm/page-writeback.c | |
parent | a5377831eb64c1b8a7b911dc79aec73a930e95da (diff) | |
download | talos-op-linux-7d33939f475d403e79124e3143d7951dcfe8629f.tar.gz talos-op-linux-7d33939f475d403e79124e3143d7951dcfe8629f.zip |
tipc: delay delete of link when failover is needed
When a bearer is disabled, all its attached links are deleted.
Ideally, we should do link failover to redundant links on other bearers,
if there are any, in such cases. This would be consistent with current
behavior when a link is reset, but not deleted. However, due to the
complexity involved, and the (wrongly) perceived low demand for this
feature, it was never implemented until now.
We mark the doomed link for deletion with a new flag, but wait until the
failover process is finished before we actually delete it. With the
improved link tunnelling/failover code introduced earlier in this commit
series, it is now easy to identify a spot in the code where the failover
is finished and it is safe to delete the marked link. Moreover, the test
for the flag and the deletion can be done synchronously, and outside the
most time critical data path.
Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Reviewed-by: Ying Xue <ying.xue@windriver.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'mm/page-writeback.c')
0 files changed, 0 insertions, 0 deletions