RFC transfer ASYNC vmscan writeback IO to the flusher threads
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest5 patches 24 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | writeback: introduce wbc.for_sync to cover the two sync stagesfs/ include/ | +7 | 2 replies | |
| 2/5 | writeback: stop periodic/background work on seeing sync worksfs/ include/ mm/ | +20 | 12 replies | |
| 3/5 | writeback: prevent sync livelock with the sync_after timestampfs/ include/ | +8 | 2 replies | |
| 4/5 | writeback: introduce bdi_start_inode_writeback()fs/ include/ | +66 | 0 replies | |
| 5/5 | vmscan: transfer async file writeback to the flushermm/ | +7 | 0 replies |
Reviews trailers per patch
1 of 5 patches has a Reviewed-by or Acked-by.
| Patch | Wu Fengguang |
|---|---|
| 1/5 | |
| 2/5 | R-b R-b |
| 3/5 | |
| 4/5 | |
| 5/5 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/5] [RFC] transfer ASYNC vmscan writeback IO to the flusher threads
Andrew,
It's possible to transfer ASYNC vmscan writeback IOs to the flusher threads. This simple patchset shows the basic idea. Since it's a big behavior change, there are inevitably lots of details to sort out. I don't know where it will go after tests and discussions, so the patches are intentionally kept simple.
sync livelock avoidance (need more to be complete, but this is minimal required for the last two patches)
[PATCH 1/5] writeback: introduce wbc.for_sync to cover the two sync stages [PATCH 2/5] writeback: stop periodic/background work on seeing sync works
[PATCH 3/5] writeback: prevent sync livelock with the sync_after timestamp
let the flusher threads do ASYNC writeback for pageout()
[PATCH 4/5] writeback: introduce bdi_start_inode_writeback() [PATCH 5/5] vmscan: transfer async file writeback to the flusher
The last two patches are the meats, they depend on the first three patches to kick the background writeback work, so that the for_reclaim writeback can be serviced timely.
Comments are welcome!
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>