From: Wei Yongjun <yjwei@cn.fujitsu.com>
To: Luo Chunbo <chunbo.luo@windriver.com>
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>,
davem@davemloft.net, netdev@vger.kernel.org,
linux-sctp@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sctp: fix the check for path failure detection
Date: Mon, 24 Aug 2009 07:54:28 +0000 [thread overview]
Message-ID: <4A924734.6000702@cn.fujitsu.com> (raw)
In-Reply-To: <1251080117.6513.11.camel@pek-cluo-desktop>
Luo Chunbo дµÀ:
> On Fri, 2009-08-21 at 17:47 -0400, Vlad Yasevich wrote:
>
>> Chunbo Luo wrote:
>>
>>> The transport is marked DOWN immediately after sending the max+1 HB,
>>> which is equal to not sending the max+1 HB at all. We should wait
>>> a next period and make sure the last HB is not acknowledged.
>>>
>>>
>> I don't think this code does what you want either...
>>
>> Let's say path_max_rxt = 2. What we'll get is:
>> timeout:
>> err++ (1)
>> if (err > 2) false
>> send HB
>> reset timer
>> timeout:
>> err++ (2)
>> if (err > 2) false
>> send HB
>> reset timer
>> timeout:
>> err++ (3)
>> if (err > 2)
>> set transport DOWN
>> send HB
>> reset timer.
>>
>> We only had 2 unacknowledged HB when we should have had 3.
>>
>
> The error count is increment after the HB was sent, and the error count
> check is before sending HB.
>
> Let's say path_max_rxt =2 . What we really get is:
>
> timeout:
> if( err > 2) false
> send HB
> err++ (1)
> reset timer
> timeout:
> if( err > 2) false
> send HB
> err++ (2)
> reset timer
> timeout:
> if( err > 2) false
> send HB
> err++ (3)
> reset timer
> timeout:
> if( err > 2)
> set transport DOWN
> send HB
> reset timer
>
> Here We had 3 unacknowledged HBs
But with Vlad's advice, you just need to do little change to the kernel
codes, may be two lines's patch, and it can do the same thing.
WARNING: multiple messages have this Message-ID (diff)
From: Wei Yongjun <yjwei@cn.fujitsu.com>
To: Luo Chunbo <chunbo.luo@windriver.com>
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>,
davem@davemloft.net, netdev@vger.kernel.org,
linux-sctp@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sctp: fix the check for path failure detection
Date: Mon, 24 Aug 2009 15:54:28 +0800 [thread overview]
Message-ID: <4A924734.6000702@cn.fujitsu.com> (raw)
In-Reply-To: <1251080117.6513.11.camel@pek-cluo-desktop>
Luo Chunbo 写道:
> On Fri, 2009-08-21 at 17:47 -0400, Vlad Yasevich wrote:
>
>> Chunbo Luo wrote:
>>
>>> The transport is marked DOWN immediately after sending the max+1 HB,
>>> which is equal to not sending the max+1 HB at all. We should wait
>>> a next period and make sure the last HB is not acknowledged.
>>>
>>>
>> I don't think this code does what you want either...
>>
>> Let's say path_max_rxt = 2. What we'll get is:
>> timeout:
>> err++ (1)
>> if (err > 2) false
>> send HB
>> reset timer
>> timeout:
>> err++ (2)
>> if (err > 2) false
>> send HB
>> reset timer
>> timeout:
>> err++ (3)
>> if (err > 2)
>> set transport DOWN
>> send HB
>> reset timer.
>>
>> We only had 2 unacknowledged HB when we should have had 3.
>>
>
> The error count is increment after the HB was sent, and the error count
> check is before sending HB.
>
> Let's say path_max_rxt =2 . What we really get is:
>
> timeout:
> if( err > 2) false
> send HB
> err++ (1)
> reset timer
> timeout:
> if( err > 2) false
> send HB
> err++ (2)
> reset timer
> timeout:
> if( err > 2) false
> send HB
> err++ (3)
> reset timer
> timeout:
> if( err > 2)
> set transport DOWN
> send HB
> reset timer
>
> Here We had 3 unacknowledged HBs
But with Vlad's advice, you just need to do little change to the kernel
codes, may be two lines's patch, and it can do the same thing.
next prev parent reply other threads:[~2009-08-24 7:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 7:04 [PATCH] sctp: fix the check for path failure detection Chunbo Luo
2009-08-21 7:04 ` Chunbo Luo
2009-08-21 21:47 ` Vlad Yasevich
2009-08-21 21:47 ` Vlad Yasevich
2009-08-24 2:15 ` Luo Chunbo
2009-08-24 2:15 ` Luo Chunbo
2009-08-24 7:54 ` Wei Yongjun [this message]
2009-08-24 7:54 ` Wei Yongjun
2009-08-24 9:35 ` Luo Chunbo
2009-08-24 9:35 ` Luo Chunbo
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=4A924734.6000702@cn.fujitsu.com \
--to=yjwei@cn.fujitsu.com \
--cc=chunbo.luo@windriver.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vladislav.yasevich@hp.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.