From: YOSHIFUJI Hideaki <hideaki.yoshifuji@miraclelinux•com>
To: Ulf Samuelsson <ulf.samuelsson@ericsson•com>, netdev@emagii•com
Cc: hideaki.yoshifuji@miraclelinux•com, netdev@vger•kernel.org
Subject: Re: [PATCH] neighbour.c: Avoid GC directly after state change
Date: Mon, 20 Apr 2015 11:33:36 +0900 [thread overview]
Message-ID: <55346580.6060801@miraclelinux.com> (raw)
In-Reply-To: <5530BE40.1000504@ericsson.com>
Hi,
Ulf Samuelsson wrote:
>> From RFC2461:
>>
>> | REACHABLE Roughly speaking, the neighbor is known to have been
>> | reachable recently (within tens of seconds ago).
>> :
>> | STALE The neighbor is no longer known to be reachable but
>> | until traffic is sent to the neighbor, no attempt
>> | should be made to verify its reachability.
>> | DELAY The neighbor is no longer known to be reachable, and
>> | traffic has recently been sent to the neighbor.
>> | Rather than probe the neighbor immediately, however,
>> | delay sending probes for a short while in order to
>> | give upper layer protocols a chance to provide
>> | reachability confirmation.
>>
>>
>
> It is all depending on the meaning of the word "recently".
> You imply, that if timeouts have been triggered, then it is no longer "recent",
> but that is not the only interpretation, it is up to the implementer to decide
> what is "recently".
That quoted text is just a "brief" description. The document has detailed
state machine.
> Therefore, if a timeout occurs due to no traffic, they must be probed before
> they are garbage collected.
It is what we do in PROBE state.
> If this is not acceptable, how do you propose to solve the problem that you cannot
> make remote units inaccessible for more than a fraction of a second?
How many neighbors do you want to maintain?
I guess you have to increase the number of gc_thresh1.
--
Hideaki Yoshifuji <hideaki.yoshifuji@miraclelinux•com>
Technical Division, MIRACLE LINUX CORPORATION
next prev parent reply other threads:[~2015-04-20 2:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 21:01 [PATCH] neighbour.c: Avoid GC directly after state change Ulf Samuelsson
2015-03-12 18:26 ` David Miller
2015-03-17 23:33 ` Ulf Samuelsson
2015-03-18 1:56 ` YOSHIFUJI Hideaki/吉藤英明
2015-04-10 8:26 ` Ulf Samuelsson
2015-04-15 13:40 ` Ulf Samuelsson
2015-04-16 5:16 ` YOSHIFUJI Hideaki
2015-04-17 8:03 ` Ulf Samuelsson
2015-04-20 2:33 ` YOSHIFUJI Hideaki [this message]
2015-04-20 12:48 ` Ulf Samuelsson
2015-04-21 3:58 ` YOSHIFUJI Hideaki
2015-04-22 7:42 ` Ulf Samuelsson
2015-04-22 10:46 ` YOSHIFUJI Hideaki
2015-04-22 11:49 ` Ulf Samuelsson
2015-05-08 9:39 ` Ulf Samuelsson
-- strict thread matches above, loose matches on Subject: below --
2015-03-11 20:28 Ulf Samuelsson
2015-03-15 8:27 ` YOSHIFUJI Hideaki
2015-03-15 19:34 ` Ulf Samuelsson
2015-03-16 4:57 ` YOSHIFUJI Hideaki/吉藤英明
2015-03-16 19:55 ` Ulf Samuelsson
2015-03-17 12:31 ` YOSHIFUJI Hideaki
2015-03-17 23:27 ` Ulf Samuelsson
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=55346580.6060801@miraclelinux.com \
--to=hideaki.yoshifuji@miraclelinux$(echo .)com \
--cc=netdev@emagii$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=ulf.samuelsson@ericsson$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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