From: jamal <hadi@cyberus.ca>
To: Steve Wise <swise@opengridcomputing.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH 0/2][RFC] Network Event Notifier Mechanism
Date: Thu, 22 Jun 2006 16:56:01 -0400 [thread overview]
Message-ID: <1151009762.5392.126.camel@jzny2> (raw)
In-Reply-To: <1151008816.3040.60.camel@stevo-desktop>
On Thu, 2006-22-06 at 15:40 -0500, Steve Wise wrote:
> On Thu, 2006-06-22 at 15:43 -0400, jamal wrote:
> >
> > No - what these 2 gents are saying was these events and infrastructure
> > already exist.
>
> Notification of the exact events needed does not exist today.
>
Ok, so you cant event make use of anything that already exists?
Or is a subset of what you need already there?
> The key events, again, are:
>
> - the neighbour entry mac address has changed.
>
>
> - the next hop ip address (ie the neighbour) for a given dst_entry has
> changed.
I dont see a difference for the above two from an L2 perspective.
Are you keeping track of IP addresses?
You didn't answer my question in the previous email as to what RDMA
needs to keep track of in hardware.
>
> - the path mtu for a given dst_entry has changed.
>
Same with this.
cheers,
jamal
next prev parent reply other threads:[~2006-06-22 20:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 18:45 [PATCH 0/2][RFC] Network Event Notifier Mechanism Steve Wise
2006-06-21 18:45 ` [PATCH 1/2] " Steve Wise
2006-06-21 18:45 ` [PATCH 2/2] Core network changes to support network event notification Steve Wise
2006-06-21 19:08 ` [PATCH 0/2][RFC] Network Event Notifier Mechanism 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 [this message]
2006-06-23 13:17 ` Steve Wise
-- strict thread matches above, loose matches on Subject: below --
2006-06-22 22:11 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
2006-06-22 22:39 Caitlin Bestler
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=1151009762.5392.126.camel@jzny2 \
--to=hadi@cyberus.ca \
--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).