A "compact_daemon_wake" vmstat exists that represents the number of times
kcompactd has woken up. This doesn't represent how much work it actually
did, though.
It's useful to understand how much compaction work is being done by
kcompactd versus other methods such as direct compaction and explicit
On Thu, 8 Dec 2016, Vlastimil Babka wrote:
> > A "compact_daemon_wake" vmstat exists that represents the number of times
> > kcompactd has woken up. This doesn't represent how much work it actually
> > did, though.
> >
> > It's useful to understand how much compaction work is being done by
> > k
On 12/08/2016 02:50 AM, David Rientjes wrote:
A "compact_daemon_wake" vmstat exists that represents the number of times
kcompactd has woken up. This doesn't represent how much work it actually
did, though.
It's useful to understand how much compaction work is being done by
kcompactd versus othe
On Thu 08-12-16 09:04:12, Vlastimil Babka wrote:
> On 12/08/2016 02:50 AM, David Rientjes wrote:
> > A "compact_daemon_wake" vmstat exists that represents the number of times
> > kcompactd has woken up. This doesn't represent how much work it actually
> > did, though.
> >
> > It's useful to under
4 matches
Mail list logo