Re: [RFC v2 0/4] Outsourcing compaction for THP allocations to kcompactd

[Rik van Riel <riel@redhat.com>]

On 07/02/2015 04:46 AM, Vlastimil Babka wrote:
> This RFC series is another evolution of the attempt to deal with THP
> allocations latencies. Please see the motivation in the previous version [1]
>
> The main difference here is that I've bitten the bullet and implemented
> per-node kcompactd kthreads - see Patch 1 for the details of why and how.
> Trying to fit everything into khugepaged was getting too clumsy, and kcompactd
> could have more benefits, see e.g. the ideas here [2]. Not everything is
> implemented yet, though, I would welcome some feedback first.

This leads to a few questions, one of which has an obvious answer.

1) Why should this functionality not be folded into kswapd?

    (because kswapd can get stuck on IO for long periods of time)

2) Given that kswapd can get stuck on IO for long periods of
    time, are there other tasks we may want to break out of
    kswapd, in order to reduce page reclaim latencies for things
    like network allocations?

    (freeing clean inactive pages?)

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>