From: Chang <changxiangzhong@gmail.com>
To: Vlad Yasevich <vyasevich@gmail.com>,
nhorman@tuxdriver.com, davem@davemloft.net
Cc: linux-sctp@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: sctp: set chunk->tsn_gap_acked at the end of cycle
Date: Sat, 23 Nov 2013 11:14:12 +0000 [thread overview]
Message-ID: <52908E04.40200@gmail.com> (raw)
In-Reply-To: <528FDF52.4030500@gmail.com>
Hi,
Could you please why a **reneged** newly acked TSN doesn't qualify the
highest_new_tsn? What's the wrongs of doing that?
I've been thinking a few scenarios, but I couldn't figure out what's
wrong with that.
WARNING: multiple messages have this Message-ID (diff)
From: Chang <changxiangzhong@gmail.com>
To: Vlad Yasevich <vyasevich@gmail.com>,
nhorman@tuxdriver.com, davem@davemloft.net
Cc: linux-sctp@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: sctp: set chunk->tsn_gap_acked at the end of cycle
Date: Sat, 23 Nov 2013 12:14:12 +0100 [thread overview]
Message-ID: <52908E04.40200@gmail.com> (raw)
In-Reply-To: <528FDF52.4030500@gmail.com>
Hi,
Could you please why a **reneged** newly acked TSN doesn't qualify the
highest_new_tsn? What's the wrongs of doing that?
I've been thinking a few scenarios, but I couldn't figure out what's
wrong with that.
next prev parent reply other threads:[~2013-11-23 11:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 7:49 [PATCH] net: sctp: set chunk->tsn_gap_acked at the end of cycle Chang Xiangzhong
2013-11-22 7:49 ` Chang Xiangzhong
2013-11-22 12:10 ` Neil Horman
2013-11-22 12:10 ` Neil Horman
2013-11-22 14:27 ` Vlad Yasevich
2013-11-22 14:27 ` Vlad Yasevich
2013-11-22 19:24 ` Chang
2013-11-22 19:24 ` Chang
2013-11-22 22:48 ` Vlad Yasevich
2013-11-22 22:48 ` Vlad Yasevich
2013-11-23 8:22 ` Chang
2013-11-23 8:22 ` Chang
2013-11-23 11:14 ` Chang [this message]
2013-11-23 11:14 ` Chang
2013-11-23 19:37 ` Vlad Yasevich
2013-11-23 19:37 ` Vlad Yasevich
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=52908E04.40200@gmail.com \
--to=changxiangzhong@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vyasevich@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.