From: yzhu1 <Yanjun.Zhu@windriver.com>
To: YOSHIFUJI Hideaki <hideaki.yoshifuji@miraclelinux.com>,
<lizefan@huawei.com>, <netdev@vger.kernel.org>,
<ulf.samuelsson@ericsson.com>, <yoshfuji@linux-ipv6.org>,
<Alexandre.Dietsch@windriver.com>
Subject: Re: [PATCH for kernel 3.4.x 1/1] net: neighbour: Add mcast_resolicit to configure the number of multicast resolicitations in PROBE state
Date: Wed, 25 Mar 2015 14:40:40 +0800 [thread overview]
Message-ID: <55125868.9020902@windriver.com> (raw)
In-Reply-To: <55113DFA.9080608@miraclelinux.com>
On 03/24/2015 06:35 PM, YOSHIFUJI Hideaki wrote:
> Hi.
>
> Zhu Yanjun wrote:
>
>> We send unicast neighbor (ARP or NDP) solicitations ucast_probes
>> times in PROBE state. Zhu Yanjun reported that some implementation
>> does not reply against them and the entry will become FAILED, which
>> is undesirable.
>>
>> We had been dealt with such nodes by sending multicast probes mcast_
>> solicit times after unicast probes in PROBE state. In 2003, I made
> I? Or please Add the From: to change the author to me.
>
>> a change not to send them to improve compatibility with IPv6 NDP.
>>
>> Let's introduce per-protocol per-interface sysctl knob "mcast_
>> reprobe" to configure the number of multicast (re)solicitation for
>> reconfirmation in PROBE state. The default is 0, since we have
>> been doing so for 10+ years.
>>
> You should say: 'This patch is based on commit foobar ("title") by
> author...' or something here.
>
>> Reported-by: Zhu Yanjun <Yanjun.Zhu@windriver.com>
>> CC: Ulf Samuelsson <ulf.samuelsson@ericsson.com>
>> Signed-off-by: YOSHIFUJI Hideaki <hideaki.yoshifuji@miraclelinux.com>
>> Signed-off-by: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
>> [Zhu Yanjun: since kernel 3.4.x is different from mainline kernel(kernel 4.0-rcX).
>> This patch is modified a lot.]
>> Signed-off-by: Zhu Yanjun <Yanjun.Zhu@windriver.com>
>> ---
>> include/linux/neighbour.h | 1 +
>> include/net/neighbour.h | 1 +
>> net/core/neighbour.c | 20 +++++++++++++++++---
>> 3 files changed, 19 insertions(+), 3 deletions(-)
>>
>> diff --git a/include/linux/neighbour.h b/include/linux/neighbour.h
>> index b188f68..6945f4f 100644
>> --- a/include/linux/neighbour.h
>> +++ b/include/linux/neighbour.h
>> @@ -112,6 +112,7 @@ enum {
>> NDTPA_APP_PROBES, /* u32 */
>> NDTPA_UCAST_PROBES, /* u32 */
>> NDTPA_MCAST_PROBES, /* u32 */
>> + NDTPA_MCAST_REPROBES, /* u32 */
>> NDTPA_ANYCAST_DELAY, /* u64, msecs */
>> NDTPA_PROXY_DELAY, /* u64, msecs */
>> NDTPA_PROXY_QLEN, /* u32 */
> No, this breaks binary compatibility.
Sorry. My bad. I will correct.
Best Regards!
Zhu Yanjun
>
next prev parent reply other threads:[~2015-03-25 6:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 9:45 [PATCH for kernel 3.4.x 0/1] net: neighbour: Add mcast_resolicit to configure the number of multicast resolicitations in PROBE state Zhu Yanjun
2015-03-24 9:45 ` [PATCH for kernel 3.4.x 1/1] " Zhu Yanjun
2015-03-24 9:51 ` Zhu, Yanjun
2015-03-24 15:55 ` David Miller
2015-03-25 2:22 ` yzhu1
2015-03-24 10:35 ` YOSHIFUJI Hideaki
2015-03-25 6:40 ` yzhu1 [this message]
2015-03-24 11:06 ` [PATCH for kernel 3.4.x 0/1] " YOSHIFUJI Hideaki
2015-03-24 15:59 ` David Miller
2015-03-24 23:06 ` YOSHIFUJI Hideaki
2015-03-25 2:24 ` yzhu1
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=55125868.9020902@windriver.com \
--to=yanjun.zhu@windriver.com \
--cc=Alexandre.Dietsch@windriver.com \
--cc=hideaki.yoshifuji@miraclelinux.com \
--cc=lizefan@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=ulf.samuelsson@ericsson.com \
--cc=yoshfuji@linux-ipv6.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 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).