summaryrefslogtreecommitdiff
path: root/drivers/target/tcm_fc
diff options
context:
space:
mode:
authorJon Maloy <jon.maloy@ericsson.com>2017-11-08 09:59:26 +0100
committerDavid S. Miller <davem@davemloft.net>2017-11-11 15:36:05 +0900
commit8d6e79d3ce13e34957de87f7584cbf1bcde74c57 (patch)
treef15780b41b74719daa4b849b1deb2e425a10ab61 /drivers/target/tcm_fc
parent141f575f76db5a973b119146844de357b88ad36d (diff)
tipc: improve link resiliency when rps is activated
Currently, the TIPC RPS dissector is based only on the incoming packets' source node address, hence steering all traffic from a node to the same core. We have seen that this makes the links vulnerable to starvation and unnecessary resets when we turn down the link tolerance to very low values. To reduce the risk of this happening, we exempt probe and probe replies packets from the convergence to one core per source node. Instead, we do the opposite, - we try to diverge those packets across as many cores as possible, by randomizing the flow selector key. To make such packets identifiable to the dissector, we add a new 'is_keepalive' bit to word 0 of the LINK_PROTOCOL header. This bit is set both for PROBE and PROBE_REPLY messages, and only for those. It should be noted that these packets are not part of any flow anyway, and only constitute a minuscule fraction of all packets sent across a link. Hence, there is no risk that this will affect overall performance. Acked-by: Ying Xue <ying.xue@windriver.com> Signed-off-by: Jon Maloy <jon.maloy@ericsson.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/target/tcm_fc')
0 files changed, 0 insertions, 0 deletions