Re: [PATCH] mm: vmscan: check mem cgroup over reclaimed

[Hillf Danton]

On Wed, Jan 25, 2012 at 7:22 AM, Ying Han <yinghan@xxxxxxxxxx> wrote:
> On Mon, Jan 23, 2012 at 7:45 PM, Hillf Danton <dhillf@xxxxxxxxx> wrote:
>> With soft limit available, what if nr_to_reclaim set to be the number of
>> pages exceeding soft limit? With over reclaim abused, what are the targets
>> of soft limit?
>
> The nr_to_reclaim is set to SWAP_CLUSTER_MAX (32) for direct reclaim
> and ULONG_MAX for background reclaim. Not sure we can set it, but it
> is possible the res_counter_soft_limit_excess equal to that target
> value. The current soft limit mechanism provides a clue of WHERE to
> reclaim pages when there is memory pressure, it doesn't change the
> reclaim target as it was before.
>

Decrement in sc->nr_to_reclaim was tried in another patch, you already saw it.

> Overreclaim a cgroup under its softlimit is bad, but we should be
> careful not introducing side effect before providing the guarantee.

Yes 8-)

> Here, the should_continue_reclaim() has logic of freeing a bit more
> order-0 pages for compaction. The logic got changed after this.
>

Compaction is to increase the successful rate of THP allocation, and in turn
to back up higher performance. In soft limit, performance guarantee is not
extra request but treated with less care.

Which one you prefer, compaction or guarantee?

Thanks
Hillf
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/