From: Wei Yongjun <yjwei@cn.fujitsu.com>
To: linux-sctp@vger.kernel.org
Subject: Re: Gap is only retransmitted once
Date: Thu, 03 Mar 2011 09:27:12 +0000 [thread overview]
Message-ID: <4D6F5EF0.50301@cn.fujitsu.com> (raw)
In-Reply-To: <AANLkTi=gP1+PTa4J+CYzpA8NCmasiMXS_p4P-zXAkyXK@mail.gmail.com>
> More read about the ethreal captures.
>
> The peer shutdown association 6 seconds after it missed the
> retransmittion of sctp.data_tsn = 447375618. During the 6 seconds,
> the peer sent a lot of SACKs but Linux did not retransmit the chunk.
>
> Could someone look at it?
I will post a patch about this, can you try it and tell us whether
the patch can fix your problem?
> Great thanks!
>
> 2011/3/3 Mingyuan Zhu <liyha.zhu@gmail.com>:
>> I attached more capture packets.
>> From the ethreal file, I found some chunks are retransmitted the
>> second time after 3 seconds. The peer does not shutdown the
>> association. But sometimes the peer shutdown the association.
>> For example:
>> sctp.data_tsn = 447375491 or sctp.data_tsn = 447375492 are
>> retransmitted 3 seconds after the first retransmittion.
>>
>> And sctp.data_tsn = 447375618, the peer shutdown association before
>> the 2nd retransmittion.
>>
>> So comes the question, why doesn't sctp retransmit immediately when it
>> receives SACK, instead it retransmit after 3 seconds?
>>
>> 2011/3/1 Mingyuan Zhu <liyha.zhu@gmail.com>:
>>> My test is working on kernel 2.6.34-4.
>>>
>>> 2011/3/1 Wei Yongjun <yjwei@cn.fujitsu.com>:
>>>>> I searched the src code. We did not use sinfo_timetolive.
>>>> I guess there were some retransmit issues in 2.6.31 and
>>>> latest kernel hit the rwnd limit, I will try to reproduce it
>>>> and fix it. wait some time since I have other work to do now.
>>>>
>>>>> 2011/3/1 Wei Yongjun <yjwei@cn.fujitsu.com>:
>>>>>> Did you using sinfo_timetolive when you send sctp message?
>>>>>> There is a bug when we handle sinfo_timetolive, I will fix this later.
>>>>>>
>>>>>>> Mingyuan Zhu wrote, at 02/22/2011 09:14 PM:
>>>>>>>> What kind of test tool you used for the testing?
>>>>>>> No test tool can directly test your case.
>>>>>>> But SCTP Conformance Test Suite Project can help you.
>>>>>>> See: http://networktest.sourceforge.net/
>>>>>>>
>>>>>>> Your case is not in the tool, so you need to write your case by yourself.
>>>>>>> data#22 has similar test procedure, see
>>>>>>> http://networktest.sourceforge.net/log/2.6.29-rc4/IPv4/data/22.html
>>>>>>>
>>>>> --
>>>>> To unsubscribe from this list: send the line "unsubscribe linux-sctp" in
>>>>> the body of a message to majordomo@vger.kernel.org
>>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>>>
next prev parent reply other threads:[~2011-03-03 9:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 13:58 Gap is only retransmitted once Mingyuan Zhu
2011-02-15 16:01 ` Vasil Velichkov
2011-02-16 4:42 ` Mingyuan Zhu
2011-02-17 3:34 ` Mingyuan Zhu
2011-02-18 14:04 ` Mingyuan Zhu
2011-02-19 8:37 ` Mingyuan Zhu
2011-02-22 6:44 ` Shan Wei
2011-02-22 13:14 ` Mingyuan Zhu
2011-03-01 1:36 ` Shan Wei
2011-03-01 2:45 ` Wei Yongjun
2011-03-01 4:39 ` Wei Yongjun
2011-03-01 4:49 ` Mingyuan Zhu
2011-03-01 8:26 ` Wei Yongjun
2011-03-01 8:47 ` Mingyuan Zhu
2011-03-03 4:44 ` Mingyuan Zhu
2011-03-03 4:49 ` Shan Wei
2011-03-03 9:27 ` Wei Yongjun [this message]
2011-03-03 10:07 ` Mingyuan Zhu
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=4D6F5EF0.50301@cn.fujitsu.com \
--to=yjwei@cn.fujitsu.com \
--cc=linux-sctp@vger.kernel.org \
/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.