Netdev List
 help / color / mirror / Atom feed
From: Steve Wise <swise@opengridcomputing.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH Round 2 0/2][RFC] Network Event Notifier Mechanism
Date: Tue, 27 Jun 2006 10:02:19 -0500	[thread overview]
Message-ID: <1151420539.3207.29.camel@stevo-desktop> (raw)
In-Reply-To: <20060627.030920.108743110.davem@davemloft.net>

On Tue, 2006-06-27 at 03:09 -0700, David Miller wrote:
> From: Steve Wise <swise@opengridcomputing.com>
> Date: Mon, 26 Jun 2006 15:36:38 -0500
> 
> > Round 2 Changes:
> > 
> > - cleaned up event structures per review feedback.
> > - began integration with netlink (see neighbour changes in patch 2).
> > - added IPv6 support.
> 
> Yes, ipv6 support is the main think I saw lacking.
> Especially the neighbour stuff.
> 
> How will you interpret the neighbour object properly, by
> looking at neigh->ops->family?
> 

Yea.

Also:  WRT a netlink message for REDIRECT events.  After thinking more
about this, it seems like users will already get notification of a
REDIRECT in the form of 2 messages, a RTM_DELROUTE for the old route and
a RTM_NEWROUTE message with the RTPROT_REDIRECT protocol type.  I think
this is perhaps sufficient for user mode notifications.  What do you
think?

For the RDMA kernel subsystem, however, we still need a specific event.
We need both the old and new dst_entry struct ptrs to figure out which
active connections were using the old dst_entry and should be updated to
use the new dst_entry.

Steve.



  reply	other threads:[~2006-06-27 15:02 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 [this message]
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
  -- 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=1151420539.3207.29.camel@stevo-desktop \
    --to=swise@opengridcomputing.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.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