From: yisupeng@gmail.com (Shawn Peng)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Question about arp caches
Date: Tue, 29 Nov 2016 02:19:19 -0500 [thread overview]
Message-ID: <caa2636f-db4e-b831-2ade-5b585f767c0e@gmail.com> (raw)
In-Reply-To: <CAEXHiZEbXu--FcFYe-fQdaaRUiqmYHXitA++NhT_C+30FvnuYA@mail.gmail.com>
I find a lot references of the function neigh_release(), can you direct
me to the one that releases a staled arp entry? Thanks.
On 11/29/2016 12:50 AM, Anupam Kapoor wrote:
>
> On Tue, Nov 29, 2016 at 10:40 AM, Shawn Peng <yisupeng@gmail.com
> <mailto:yisupeng@gmail.com>> wrote:
>
> I'm reading the code about arp protocol. It seems like the kernel uses
> the neigh_table structure to keep track of caches, right?
>
> ?yes.?
>
> There should
> be some code that remove the stale entries in the cache, but I didn't
> find the code that does this job. Does anyone have an idea?
>
> ?look at neigh_release(...) and neigh_destroy(...). basically,
> neigh_release(...) decrements the reference count of a neighbor, and
> neigh_destroy(...) frees it when this reference count reaches zero.?
>
>
> ?--
> 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/20161129/e6dca7eb/attachment.html
next prev parent reply other threads:[~2016-11-29 7:19 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 [this message]
[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
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=caa2636f-db4e-b831-2ade-5b585f767c0e@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).