Netdev List
 help / color / mirror / Atom feed
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:37:52 -0700 (PDT)	[thread overview]
Message-ID: <20060627.133752.21929335.davem@davemloft.net> (raw)
In-Reply-To: <1151440399.20252.9.camel@stevo-desktop>

From: Steve Wise <swise@opengridcomputing.com>
Date: Tue, 27 Jun 2006 15:33:19 -0500

> From my experimentation with netlink, RTM_NEWROUTE and RTM_DELROUTE
> messages do not get sent up for redirect events.  I have, in fact, added
> this with the new patch I'll send out soon.  So either way I need to
> change the IPv[46] code to generate a notification for redirects.  With
> the single NETEVENT_REDIRECT call, the RDMA driver can, in one sweep,
> update all the connections.  It seems more efficient.  At the place
> where I've hooked redirect, both the old route and the new route are
> already created.

Ok, let's see what it looks like.

  reply	other threads:[~2006-06-27 20:37 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
2006-06-27 20:33           ` Steve Wise
2006-06-27 20:37             ` David Miller [this message]
  -- 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.133752.21929335.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