On Tue, 2007-09-11 at 22:31 -0400, John Stoffel wrote: I hope the snipped questions were sufficiently answered in the other mail. If not, holler :-) > Peter> 3 is done by also scaling the dirty limit proportional to the > Peter> current task's recent dirty rate. > > Do you mean task or device here? I'm just wondering how well this > works with a bunch of devices with wildly varying speeds. Task. What I do is modify the limit like this: current_limit = dirty_limit * p(bdi_writeout) * (1 - p(task_dirty)/8) Where the p() values are [0, 1]. By including the inverse of the task dirty rate one gets that tasks that are more agressive dirtiers get throttled more aggressively, whereas tasks that occasionally dirty a page get a little more room.
Attachment:
signature.asc
Description: This is a digitally signed message part
- References:
- [PATCH 00/23] per device dirty throttling -v10
- From: Peter Zijlstra <[email protected]>
- Re: [PATCH 00/23] per device dirty throttling -v10
- From: "John Stoffel" <[email protected]>
- [PATCH 00/23] per device dirty throttling -v10
- Prev by Date: [PATCH] Fix hci_sock build with CONFIG_COMPAT=n
- Next by Date: Re: clockevents: fix resume logic
- Previous by thread: Re: [PATCH 00/23] per device dirty throttling -v10
- Next by thread: Re: [PATCH 00/23] per device dirty throttling -v10
- Index(es):
 |