Consolidate IP fragment management
Status from this message: Applied.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/9 | Move common fields from frag_queues in one placeinclude/ net/ net/ +1 more | +232 | 1 reply | |
| 2/9 | Collect frag queues management objects togetherinclude/ include/ include/ +7 more | +224 | 1 reply | |
| 3/9 | Collect common sysctl variables togetherinclude/ include/ include/ +7 more | +82 | 1 reply | |
| 4/9 | Consolidate the xxx_frag_killinclude/ net/ net/ +2 more | +28 | 1 reply | |
| 5/9 | Consolidate xxx_the secret_rebuildinclude/ net/ net/ +2 more | +52 | 1 reply | |
| 6/9 | Consolidate the xxx_frag_destroyinclude/ net/ net/ +2 more | +74 | 1 reply | |
| 7/9 | Consolidate the xxx_evictorinclude/ include/ include/ +4 more | +52 | 1 reply | |
| 8/9 | Small cleanup for xxx_put after evictor consolidationnet/ net/ net/ | +16 | 1 reply | |
| 9/9 | Consolidate the xxx_putinclude/ net/ net/ +1 more | +9 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/9] Consolidate IP fragment management
Patrick recently pointed out, that there are three places that perform IP fragments management. In ipv4, ipv6 and in ip6 conntracks. Looks like these places can be a bit consolidated.
The proposal is to create a common structure inet_frag_queue to put common fields like list heads, refcounts etc in, and include it into the specific fragment queues. Then such objects like hash tables, lists, locks etc are moved to common place (struct inet_frags). At the end common code is moved to the net/ipv4/inet_fragment.c.
The inet_ prefix in file names, data structures and functions, and the code place (net/ipv4) was proposed by Alexey, but the exact names were selectd by me, so maybe there can be a better ones.