From: David Miller <davem@davemloft.net>
To: jon.maloy@ericsson.com
Cc: netdev@vger.kernel.org,
mohan.krishna.ghanta.krishnamurthy@ericsson.com,
tung.q.nguyen@dektech.com.au, hoang.h.le@dektech.com.au,
canh.d.luu@dektech.com.au, ying.xue@windriver.com,
tipc-discussion@lists.sourceforge.net
Subject: Re: [net-next v2 1/1] tipc: improve link resiliency when rps is activated
Date: Sat, 11 Nov 2017 15:36:33 +0900 (KST) [thread overview]
Message-ID: <20171111.153633.2266031879610202255.davem@davemloft.net> (raw)
In-Reply-To: <1510131566-30308-1-git-send-email-jon.maloy@ericsson.com>
From: Jon Maloy <jon.maloy@ericsson.com>
Date: Wed, 8 Nov 2017 09:59:26 +0100
> 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>
Applied, thanks.
prev parent reply other threads:[~2017-11-11 6:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 8:59 [net-next v2 1/1] tipc: improve link resiliency when rps is activated Jon Maloy
2017-11-11 6:36 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171111.153633.2266031879610202255.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=canh.d.luu@dektech.com.au \
--cc=hoang.h.le@dektech.com.au \
--cc=jon.maloy@ericsson.com \
--cc=mohan.krishna.ghanta.krishnamurthy@ericsson.com \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=tung.q.nguyen@dektech.com.au \
--cc=ying.xue@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).