per device dirty throttling -v3
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest12 patches 14 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/12 | nfs: remove congestion_end()fs/ include/ mm/ | +1 | 0 replies | |
| 2/12 | mm: scalable bdi statistics counters.block/ drivers/ drivers/ +5 more | +209 | 2 replies | |
| 3/12 | mm: count dirty pages per BDIfs/ include/ mm/ +1 more | +5 | 0 replies | |
| 4/12 | mm: count writeback pages per BDIinclude/ mm/ | +7 | 0 replies | |
| 5/12 | mm: count unstable pages per BDIfs/ include/ | +5 | 0 replies | |
| 6/12 | mm: expose BDI statistics in sysfs.block/ | +32 | 0 replies | |
| 7/12 | mm: per device dirty thresholdinclude/ mm/ mm/ | +145 | 0 replies | |
| 8/12 | mm: fixup possible deadlockinclude/ mm/ mm/ | +52 | 1 reply | |
| 9/12 | mm: remove throttle_vm_writebackinclude/ mm/ mm/ | +0 | 2 replies | |
| 10/12 | mm: page_alloc_waitarch/ fs/ include/ +3 more | +31 | 2 replies | |
| 11/12 | mm: accurate pageout congestion waitinclude/ mm/ mm/ | +30 | 2 replies | |
| 12/12 | mm: per BDI congestion feedbackdrivers/ drivers/ fs/ +12 more | +88 | 4 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 00/12] per device dirty throttling -v3
Against 2.6.21-rc5-mm4 without:
per-backing_dev-dirty-and-writeback-page-accounting.patch
This series implements BDI independent dirty limits and congestion control.
This should solve several problems we currently have in this area:
- mutual interference starvation (for any number of BDIs), and
- deadlocks with stacked BDIs (loop and FUSE).
All the fancy new congestion code has been compile and boot tested, but not much more. I'm posting to get feedback on the ideas.
--
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>