From: David Miller <davem@davemloft.net>
To: jon.maloy@ericsson.com
Cc: netdev@vger.kernel.org, paul.gortmaker@windriver.com,
erik.hugne@ericsson.com, ying.xue@windriver.com,
maloy@donjonn.com, tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH net 1/1] tipc: fix problem with parallel link synchronization mechanism
Date: Wed, 29 Apr 2015 15:09:23 -0400 (EDT) [thread overview]
Message-ID: <20150429.150923.1291697432920867232.davem@davemloft.net> (raw)
In-Reply-To: <1430254744-10081-1-git-send-email-jon.maloy@ericsson.com>
From: Jon Maloy <jon.maloy@ericsson.com>
Date: Tue, 28 Apr 2015 16:59:04 -0400
> Currently, we try to accumulate arrived packets in the links's
> 'deferred' queue during the parallel link syncronization phase.
>
> This entails two problems:
>
> - With an unlucky combination of arriving packets the algorithm
> may go into a lockstep with the out-of-sequence handling function,
> where the synch mechanism is adding a packet to the deferred queue,
> while the out-of-sequence handling is retrieving it again, thus
> ending up in a loop inside the node_lock scope.
>
> - Even if this is avoided, the link will very often send out
> unnecessary protocol messages, in the worst case leading to
> redundant retransmissions.
>
> We fix this by just dropping arriving packets on the upcoming link
> during the synchronization phase, thus relying on the retransmission
> protocol to resolve the situation once the two links have arrived to
> a synchronized state.
>
> Reviewed-by: Erik Hugne <erik.hugne@ericsson.com>
> Reviewed-by: Ying Xue <ying.xue@windriver.com>
> Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Applied, thanks Jon.
prev parent reply other threads:[~2015-04-29 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 20:59 [PATCH net 1/1] tipc: fix problem with parallel link synchronization mechanism Jon Maloy
2015-04-29 19:09 ` 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=20150429.150923.1291697432920867232.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=erik.hugne@ericsson.com \
--cc=jon.maloy@ericsson.com \
--cc=maloy@donjonn.com \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=tipc-discussion@lists.sourceforge.net \
--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).