RFC VM deadlock avoidance -v9
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest6 patches 17 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | mm: slab allocation fairnessmm/ mm/ mm/ | +142 | 11 replies | |
| 2/6 | mm: allow PF_MEMALLOC from softirq contextkernel/ mm/ | +11 | 0 replies | |
| 3/6 | mm: serialize access to min_free_kbytesmm/ | +13 | 0 replies | |
| 4/6 | mm: emergency pool and __GFP_EMERGENCYinclude/ include/ mm/ +2 more | +59 | 0 replies | |
| 5/6 | slab: kmem_cache_objs_to_pages()include/ mm/ | +7 | 5 replies | |
| 6/6 | net: vm deadlock avoidance coreinclude/ include/ net/ +12 more | +312 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC][PATCH 0/6] VM deadlock avoidance -v9
Hi,
I have a new version of these patches; I'm still using SOCK_VMIO socket tagging and skb->emergency marks, since I have not come up with another approach that might work and my RFC to netdev has so far been ignored.
Other than this though, it changed quite a bit;
- I now use the regular allocation paths and cover all allocations
needed to process a skb (although the RX pool sizing might need more variables)
- The emergency RX pool size is based on ip[46]frag_high_thresh and
ip[46]_rt_max_size so that fragment assembly and dst route cache allocations cannot exhaust the memory. (more paths need analysis xfrm, conntrack?)
- skb->emergency packets skip taps
- skb->emergency packets warn about and ignores NF_QUEUE targets
The patches definitely need more work but would you agree with the general direction I'm working in or would you suggest yet another direction?
Kind regards,
Peter
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>