RFC Network Event Notifier Mechanism
Get series with b4
b4 am 20060621184519.10425.69175.stgit@stevo-desktopVersions newest first
- v1 RFC Latest2 patches 13 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | Network Event Notifier Mechanism.include/ net/ | +108 | 0 replies | |
| 2/2 | Core network changes to support network event notification.net/ net/ net/ +1 more | +22 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2][RFC] Network Event Notifier Mechanism
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, path MTU changes, and route changes.
The reason these devices need update events is because they typically cache this information in hardware and need to be notified when this information has been updated.
This approach is one of many possibilities and may be preferred because it uses an existing notification mechanism that has precedent in the stack. An alternative would be to add a netdev method to notify affect devices of these events.
This code does not yet implement path MTU change because the number of places in which this value is updated is large and if this mechanism seems reasonable, it would be probably be best to funnel these updates through a single function.
We would like to get this or similar functionality included in 2.6.19 and request comments.
This patchset consists of 2 patches:
1) New files implementing the Network Event Notifier
2) Core network changes to generate network event notifications