From: David Miller <davem@davemloft.net>
To: swise@opengridcomputing.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH Round 2 0/2][RFC] Network Event Notifier Mechanism
Date: Tue, 27 Jun 2006 13:21:32 -0700 (PDT) [thread overview]
Message-ID: <20060627.132132.21596632.davem@davemloft.net> (raw)
In-Reply-To: <1151439548.20252.2.camel@stevo-desktop>
From: Steve Wise <swise@opengridcomputing.com>
Date: Tue, 27 Jun 2006 15:19:08 -0500
> For an RDMA NIC, all this logic is in HW, which is why we need the event
> notification; to tell the HW to change its next hop information.
Back to the route change notification, I still think you can
get what you need by just looking for the route delete.
You can match if any RDMA connection is using the deleted
route, mark it "update pending" or something like that,
and when the you get the "new route" event you can walk the
"pending" list and try to relookup the route for those
connections.
next prev parent reply other threads:[~2006-06-27 20:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 20:36 [PATCH Round 2 0/2][RFC] Network Event Notifier Mechanism Steve Wise
2006-06-26 20:36 ` [PATCH Round 2 1/2] " Steve Wise
2006-06-26 20:36 ` [PATCH Round 2 2/2] Core network changes to support network event notification Steve Wise
2006-06-27 10:09 ` [PATCH Round 2 0/2][RFC] Network Event Notifier Mechanism David Miller
2006-06-27 15:02 ` Steve Wise
2006-06-27 20:14 ` David Miller
2006-06-27 20:19 ` Steve Wise
2006-06-27 20:21 ` David Miller [this message]
2006-06-27 20:33 ` Steve Wise
2006-06-27 20:37 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2006-06-27 20:27 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=20060627.132132.21596632.davem@davemloft.net \
--to=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