On 2015/12/16 20:09, Johannes Weiner wrote:
On Wed, Dec 16, 2015 at 12:18:30PM +0900, Kamezawa Hiroyuki wrote:
Hmm, my requests are
- set the same capabilities as mlock() to set swap.limit=0
Setting swap.max is already privileged operation.
Sure.
- swap-full notification via vmpressure or something mechanism.
Why?
I think it's a sign of unhealthy condition, starting file cache drop rate to
rise.
But I forgot that there are resource threshold notifier already. Does the
notifier work
for swap.usage ?
- OOM-Killer's available memory calculation may be corrupted, please check.
Vladimir updated mem_cgroup_get_limit().
I'll check it.
- force swap-in at reducing swap.limit
Why?
If full, swap.limit cannot be reduced even if there are available memory in a
cgroup.
Another cgroup cannot make use of the swap resource while it's occupied by
other cgroup.
The job scheduler should have a chance to fix the situation.
Thanks,
-Kame
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
