From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: Dave Hansen <dave.hansen@intel.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: RE: Background page clearing
Date: Fri, 25 Jul 2014 17:27:26 +0100 [thread overview]
Message-ID: <A610E03AD50BFC4D95529A36D37FA55E3756EFEC80@GEORGE.Emea.Arm.com> (raw)
In-Reply-To: <53D27590.2090500@intel.com>
> On 07/25/2014 08:06 AM, Wilco Dijkstra wrote:
> > 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).
>
> If the page is being allocated, it is about to be used and be brought in
> to the CPU's cache. If we zero it close to this use, we only pay to
> bring it in to the CPU's cache once. Or so goes the theory...
I can see the reasoning for 4KB pages and small allocations (eg. stack),
but would that ever be true for huge pages?
> I tried a zero-on-free implementation a year or so ago. It helped some
> workloads and hurt others. The gains were not large enough or
> widespread enough to merit pushing it in to the kernel.
Was that literally zero-on-free or zero in the background? Was the result
the same for different page sizes? My guess is that the result will be
different for huge pages.
Wilco
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
--
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 prev parent reply other threads:[~2014-07-25 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 15:06 Wilco Dijkstra
2014-07-25 15:19 ` Dave Hansen
2014-07-25 16:27 ` Wilco Dijkstra [this message]
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=A610E03AD50BFC4D95529A36D37FA55E3756EFEC80@GEORGE.Emea.Arm.com \
--to=wilco.dijkstra@arm.com \
--cc=dave.hansen@intel.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