From: jamal <hadi@cyberus.ca>
To: Steve Wise <swise@opengridcomputing.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, caitlinb@broadcom.com
Subject: Re: [PATCH 0/2][RFC] Network Event Notifier Mechanism
Date: Tue, 27 Jun 2006 08:44:40 -0400 [thread overview]
Message-ID: <1151412280.6516.35.camel@jzny2> (raw)
In-Reply-To: <1151332486.2398.20.camel@stevo-desktop>
On Mon, 2006-26-06 at 09:34 -0500, Steve Wise wrote:
> On Sat, 2006-06-24 at 10:30 -0400, jamal wrote:
> The route/hh cache insertions might work for the initial dst MAC per
> next-hop IP. But this dst MAC can _change_ for various reasons (even
> though the next-hop IP remains the same). Such a change, I think,
> doesn't generate a new route + hh cache insertion, just a change to the
> hh entry.
>
> Also, I think the route cache entry is created _before_ the MAC addr is
> known. So we really need to know when the neighbour entry is updated
> with the MAC address as a result of ARP/ND. Hooking the correct spot in
> the neighbour code where the mac address gets stored also gets us the
> change event I described above.
>
> Does this make sense?
>
no - but as long as you solve the problem it should be fine.
[My goal was to help -factoring in some experiences- it seems you have
it under control though].
cheers,
jamal
next prev parent reply other threads:[~2006-06-27 12:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 22:11 [PATCH 0/2][RFC] Network Event Notifier Mechanism Caitlin Bestler
2006-06-22 22:21 ` jamal
2006-06-22 22:58 ` David Miller
2006-06-23 0:56 ` jamal
2006-06-23 13:24 ` Steve Wise
2006-06-23 19:57 ` David Miller
2006-06-23 20:12 ` Steve Wise
2006-06-24 14:30 ` jamal
2006-06-26 14:34 ` Steve Wise
2006-06-27 12:44 ` jamal [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-22 22:39 Caitlin Bestler
2006-06-21 18:45 Steve Wise
2006-06-21 19:08 ` YOSHIFUJI Hideaki / 吉藤英明
2006-06-22 8:57 ` David Miller
2006-06-22 13:53 ` Steve Wise
2006-06-22 15:27 ` Steve Wise
2006-06-22 19:43 ` jamal
2006-06-22 20:18 ` Steve Wise
2006-06-22 20:36 ` jamal
2006-06-22 20:58 ` Steve Wise
2006-06-22 22:14 ` jamal
2006-06-23 13:11 ` Steve Wise
2006-06-22 20:40 ` Steve Wise
2006-06-22 20:56 ` jamal
2006-06-23 13:17 ` Steve Wise
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=1151412280.6516.35.camel@jzny2 \
--to=hadi@cyberus.ca \
--cc=caitlinb@broadcom.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=swise@opengridcomputing.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 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).