From: yisupeng@gmail.com (Yisu Peng)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Fwd: Question about arp caches
Date: Wed, 30 Nov 2016 04:45:55 -0500 [thread overview]
Message-ID: <7f9b9530-167d-0fff-fd81-258fb7ccbdde@gmail.com> (raw)
In-Reply-To: <CAEXHiZGS-RWY_PVcaMLb3iWij1_kZO8PSvTo7p5EQ-Fx-PvxkQ@mail.gmail.com>
Oh, I see. Thanks. Appreciate that.
On 11/30/2016 3:42 AM, Anupam Kapoor wrote:
>
> On Wed, Nov 30, 2016 at 1:46 PM, Yisu Peng <yisupeng@gmail.com
> <mailto:yisupeng@gmail.com>> wrote:
>
> So, how is the kernel check those staled arp entries? Or, what is
> the mechanism that the kernel uses to find the out of date entries?
>
>
> ?ok sure, well, each neighbor entry (struct neighbour) has a 'timer'
> (which is created during neighbor creation i.e.
> during neigh_alloc(...)). this timer gets 'serviced' by
> '?neigh_timer_handler(...)', which is the per neighbor garbage
> collector handler.
>
> when the state of the neighbor becomes NUD_FAILED, the neighbor is
> collected via invokation of 'neigh_release(...)' as indicated earlier.
>
> ?--
> kind regards
> anupam?
>
> In the beginning was the lambda, and the lambda was with Emacs, and
> Emacs was the lambda.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161130/980d4382/attachment.html
prev parent reply other threads:[~2016-11-30 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 5:10 Question about arp caches Shawn Peng
2016-11-29 5:50 ` Anupam Kapoor
2016-11-29 7:19 ` Shawn Peng
[not found] ` <CAEXHiZH3yHTNrN1MvsNW3dEHRJZH43vzf06X1ojcm2auO+6jdA@mail.gmail.com>
2016-11-30 6:41 ` Fwd: " Anupam Kapoor
2016-11-30 8:16 ` Yisu Peng
2016-11-30 8:42 ` Anupam Kapoor
2016-11-30 9:45 ` Yisu Peng [this message]
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=7f9b9530-167d-0fff-fd81-258fb7ccbdde@gmail.com \
--to=yisupeng@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).