Con Kolivas wrote:
>
> ...
> - swap_tendency = mapped_ratio / 2 + distress + vm_swappiness;
> + swap_tendency = mapped_ratio / 2 + distress ;
> + if (swap_tendency > 50){
> + if (vm_swappiness <= 990) vm_swappiness+=10;
> + }
> + else
> + if (vm_swappiness > 0) vm_swappiness--;
> + swap_tendency += (vm_swappiness / 10);
>
heh, that could work. So basically you're saying "the longer we're
under swap stress, the more swappy we want to get".
Problem is, users have said they don't want that. They say that they
want to copy ISO images about all day and not swap. I think.
It worries me. It means that we'll be really slow to react to sudden
load swings, and it increases the complexity of the analysis and
testing. And I really do want to give the user a single knob,
which has understandable semantics and for which I can feasibly test
all operating regions.
I really, really, really, really don't want to get too fancy in there.
I have changed this code a bit, and have added other things. Mainly
over on the writer throttling side, which tends to be the place where
the stress comes from in the first place.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Oct 07 2002 - 22:01:02 EST