Messages in this thread | | | From | Nikanth Karthikesan <> | Subject | Re: [RFC][PATCH] Per file dirty limit throttling | Date | Wed, 18 Aug 2010 14:52:04 +0530 |
| |
On Tuesday 17 August 2010 13:54:35 Peter Zijlstra wrote: > On Tue, 2010-08-17 at 10:39 +0530, Nikanth Karthikesan wrote: > > Oh, nice. Per-task limit is an elegant solution, which should help > > during most of the common cases. > > > > But I just wonder what happens, when > > 1. The dirtier is multiple co-operating processes > > 2. Some app like a shell script, that repeatedly calls dd with seek and > > skip? People do this for data deduplication, sparse skipping etc.. > > 3. The app dies and comes back again. Like a VM that is rebooted, and > > continues writing to a disk backed by a file on the host. > > > > Do you think, in those cases this might still be useful? > > Those cases do indeed defeat the current per-task-limit, however I think > the solution to that is to limit the amount of writeback done by each > blocked process. >
Blocked on what? Sorry, I do not understand.
Thanks Nikanth
> Jan Kara had some good ideas in that department. >
| |