RFC soft and dynamic dirty throttling limits
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest17 patches 31 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/17 | writeback: remove the internal 5% low bound on dirty_ratiofs/ mm/ | +6 | 4 replies | |
| 2/17 | writeback: IO-less balance_dirty_pages()include/ mm/ | +39 | 2 replies | |
| 3/17 | writeback: per-task rate limit to balance_dirty_pages()include/ mm/ | +21 | 0 replies | |
| 4/17 | writeback: quit throttling when bdi dirty/writeback pages go downmm/ | +15 | 0 replies | |
| 5/17 | writeback: quit throttling when signal pendingmm/ | +3 | 9 replies | |
| 6/17 | writeback: move task dirty fraction to balance_dirty_pages()mm/ | +6 | 0 replies | |
| 7/17 | writeback: add trace event for balance_dirty_pages()include/ mm/ | +49 | 0 replies | |
| 8/17 | writeback: account per-bdi accumulated written pagesinclude/ mm/ mm/ | +6 | 2 replies | |
| 9/17 | writeback: bdi write bandwidth estimationfs/ include/ include/ +2 more | +41 | 0 replies | |
| 10/17 | writeback: show bdi write bandwidth in debugfsmm/ | +13 | 0 replies | |
| 11/17 | writeback: make nr_to_write a per-file limitfs/ include/ | +12 | 0 replies | |
| 12/17 | writeback: scale IO chunk size up to device bandwidthfs/ | +17 | 0 replies | |
| 13/17 | writeback: reduce per-bdi dirty threshold ramp up timemm/ | +1 | 1 reply | |
| 14/17 | vmscan: add scan_control.prioritymm/ | +4 | 0 replies | |
| 15/17 | mm: lower soft dirty limits on memory pressurefs/ include/ mm/ +1 more | +55 | 1 reply | |
| 16/17 | mm: create /vm/dirty_pressure in debugfsmm/ | +27 | 0 replies | |
| 17/17 | writeback: consolidate balance_dirty_pages() variable namesmm/ | +16 | 0 replies |
Reviews trailers per patch
2 of 17 patches have a Reviewed-by or Acked-by.
| Patch | Con Kolivas | Peter Zijlstra | Rik van Riel | Neil Brown | KOSAKI Motohiro | Johannes Weiner |
|---|---|---|---|---|---|---|
| 1/17 | Proposed-by | A-b | R-b | R-b | R-b | A-b |
| 2/17 | ||||||
| 3/17 | ||||||
| 4/17 | ||||||
| 5/17 | ||||||
| 6/17 | ||||||
| 7/17 | ||||||
| 8/17 | R-b | |||||
| 9/17 | ||||||
| 10/17 | ||||||
| 11/17 | ||||||
| 12/17 | ||||||
| 13/17 | ||||||
| 14/17 | ||||||
| 15/17 | ||||||
| 16/17 | ||||||
| 17/17 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 6 reviewers.
Cover letter [PATCH 00/17] [RFC] soft and dynamic dirty throttling limits
The basic idea is to introduce a small region under the bdi dirty threshold. The task will be throttled gently when stepping into the bottom of region, and get throttled more and more aggressively as bdi dirty+writeback pages goes up closer to the top of region. At some point the application will be throttled at the right bandwidth that balances with the device write bandwidth. (the 2nd patch has more details)
The first two patch groups introduce two building blocks..
IO-less balance_dirty_pages()
[PATCH 02/17] writeback: IO-less balance_dirty_pages()
[PATCH 03/17] writeback: per-task rate limit to balance_dirty_pages() [PATCH 04/17] writeback: quit throttling when bdi dirty/writeback pages go down [PATCH 05/17] writeback: quit throttling when signal pending
(trace event)
[PATCH 06/17] writeback: move task dirty fraction to balance_dirty_pages() [PATCH 07/17] writeback: add trace event for balance_dirty_pages()
bandwidth estimation
[PATCH 08/17] writeback: account per-bdi accumulated written pages [PATCH 09/17] writeback: bdi write bandwidth estimation [PATCH 10/17] writeback: show bdi write bandwidth in debugfs
..for use by the next two features:
larger nr_to_write (hence IO size)
[PATCH 11/17] writeback: make nr_to_write a per-file limit [PATCH 12/17] writeback: scale IO chunk size up to device bandwidth
dynamic dirty pages limit
[PATCH 14/17] vmscan: add scan_control.priority [PATCH 15/17] mm: lower soft dirty limits on memory pressure [PATCH 16/17] mm: create /vm/dirty_pressure in debugfs
The following two patches can be merged independently indeed.
change of rules
[PATCH 01/17] writeback: remove the internal 5% low bound on dirty_ratio [PATCH 13/17] writeback: reduce per-bdi dirty threshold ramp up time
And this cleanup reflects a late thought, it would better to be moved to the beginning of the patch series..
cleanup
[PATCH 17/17] writeback: consolidate balance_dirty_pages() variable names
fs/fs-writeback.c | 49 ++++- include/linux/backing-dev.h | 2 include/linux/sched.h | 7 include/linux/writeback.h | 17 + include/trace/events/writeback.h | 47 +++++ mm/backing-dev.c | 29 +-- mm/page-writeback.c | 248 ++++++++++++++++------------- mm/vmscan.c | 22 ++ mm/vmstat.c | 29 +++ 9 files changed, 311 insertions(+), 139 deletions(-)
Thanks,
Fengguang
--
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>