netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Wise <swise@opengridcomputing.com>
To: davem@davemloft.net, rdreier@cisco.com
Cc: netdev@vger.kernel.org, openib-general@openib.org
Subject: [PATCH Round 5 0/3] Network Event Notifier Mechanism
Date: Fri, 28 Jul 2006 13:28:49 -0500	[thread overview]
Message-ID: <20060728182849.14325.62898.stgit@stevo-desktop> (raw)


Dave/Roland, is this patchset about ready to go?

Round 5 Changes:

- removed user-mode support
- removed route add/del events.

------

This patch implements a mechanism that allows interested clients to
register for notification of certain network events. The intended use
is to allow RDMA devices (linux/drivers/infiniband) to be notified of
neighbour updates, ICMP redirects, and path MTU changes.

RDMA devices need these network events because they typically
cache this information in hardware and need to be notified
when it changes.  To learn about RDMA internet protocols, see:
http://www.ietf.org/html.charters/rddp-charter.html.

The key events of interest are:

- neighbour mac address change 
- routing redirect (the next hop neighbour changes for a dst_entry)
- path mtu change (the path mtu for a dst_entry changes).

This patchset consists of 3 patches:

1) New files implementing the Network Event Notifier
2) Core network changes to generate netevents
3) Cleanup ib_addr modules to use the netevent patch

Signed-off-by: Tom Tucker <tom@opengridcomputing.com>
Signed-off-by: Steve Wise <swise@opengridcomputing.com>

             reply	other threads:[~2006-07-28 18:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-28 18:28 Steve Wise [this message]
2006-07-28 18:28 ` [PATCH Round 5 1/3] Network Event Notifier Mechanism Steve Wise
2006-07-28 18:29 ` [PATCH Round 5 2/3] Core net changes to generate netevents Steve Wise
2006-07-28 18:29 ` [PATCH Round 5 3/3] Cleanup ib_addr module to use the netevents Steve Wise
2006-07-31  3:45 ` [PATCH Round 5 0/3] Network Event Notifier Mechanism David Miller

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=20060728182849.14325.62898.stgit@stevo-desktop \
    --to=swise@opengridcomputing.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=openib-general@openib.org \
    --cc=rdreier@cisco.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).