From: "Wilco Dijkstra" <wdijkstr@arm.com>
To: linux-mm@kvack.org
Subject: Background page clearing
Date: Fri, 25 Jul 2014 16:06:51 +0100 [thread overview]
Message-ID: <000001cfa81a$110d15c0$33274140$@com> (raw)
Hi,
I recently noticed how a Stream benchmark took 30% more time in the first iteration due to having to
clean pages in the output array. Especially clearing a huge page on a pagefault is a substantial
overhead. It affects the cached data of the workload while it is running and reduces available
memory bandwidth.
Is there a reason Linux does not do background page clearing like other OSes to reduce this
overhead? It would be a good fit for typical mobile workloads (bursts of high activity followed by
periods of low activity).
Wilco
--
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>
next reply other threads:[~2014-07-25 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 15:06 Wilco Dijkstra [this message]
2014-07-25 15:19 ` Dave Hansen
2014-07-25 16:27 ` Wilco Dijkstra
2014-07-25 16:32 ` Dave Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000001cfa81a$110d15c0$33274140$@com' \
--to=wdijkstr@arm.com \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox