inetpeer for ipv6, take 2
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest8 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/8 | inetpeer: Abstract out the tree root accesses.net/ | +69 | 0 replies | |
| 2/8 | inetpeer: Introduce inet_peer_address_t.include/ net/ net/ | +18 | 0 replies | |
| 3/8 | inetpeer: Make inet_getpeer() take an inet_peer_adress_t pointer.include/ net/ net/ +2 more | +19 | 0 replies | |
| 4/8 | inetpeer: Abstract address comparisons.net/ | +27 | 0 replies | |
| 5/8 | inetpeer: Add v6 peers tree, abstract root properly.net/ | +18 | 0 replies | |
| 6/8 | inetpeer: Add inet_getpeer_v6()include/ | +10 | 0 replies | |
| 7/8 | ipv6: Add infrastructure to bind inet_peer objects to routes.include/ include/ net/ +1 more | +25 | 0 replies | |
| 8/8 | inet: Turn ->remember_stamp into ->get_peer in connection AF ops.include/ include/ net/ +2 more | +44 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/8] inetpeer for ipv6, take 2
Ok, this time, thanks to feedback from Eric Dumazet and others, I've taken a more systematic approach to these changes.
Now there are two seperate AVL trees for ipv4 and ipv6.
Looking further, I've considered a dumping facility for these things as currently there is no real way to monitor these tables and we surely will want to if inetpeer takes on more responsibilities.