RFC some random writeback fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest7 patches 19 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/7 | writeback: cleanup writeback_single_inode()fs/ | +7 | 1 reply | |
| 2/7 | writeback: fix queue_io() orderingfs/ | +5 | 4 replies | |
| 3/7 | writeback: merge for_kupdate and !for_kupdate requeue io logicsfs/ | +6 | 0 replies | |
| 4/7 | writeback: ensure large files are written in MAX_WRITEBACK_PAGES chunksfs/ include/ | +43 | 0 replies | |
| 5/7 | writeback: use 64MB MAX_WRITEBACK_PAGESinclude/ | +6 | 4 replies | |
| 6/7 | writeback: dont abort inode on congestionfs/ | +4 | 0 replies | |
| 7/7 | writeback: balance_dirty_pages() shall write more than dirtied pagesmm/ | +7 | 10 replies |
Reviews trailers per patch
2 of 7 patches have a Reviewed-by or Acked-by.
| Patch | Jan Kara |
|---|---|
| 1/7 | A-b |
| 2/7 | A-b |
| 3/7 | |
| 4/7 | |
| 5/7 | |
| 6/7 | |
| 7/7 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [RFC][PATCH 0/7] some random writeback fixes
Hi all,
These are some writeback fixes based on the latest linux-next without the vm.max_writeback_mb knob, since I'm not aware of any strong reasons for introducing it. Instead, the MAX_WRITEBACK_PAGES is directly increased to 64MB.
Other patches are straightforward. Needs more tests but it's enough to show the basic ideas. Comments are welcome!
Thanks,
Fengguang