From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Jan Beulich <JBeulich@suse.com>
Cc: linux-mm@kvack.org, David Vrabel <david.vrabel@citrix.com>,
mingo@elte.hu, tglx@linutronix.de,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
hpa@zytor.com
Subject: Re: [PATCH] improve __GFP_COLD/__GFP_ZERO interaction
Date: Mon, 2 Jun 2014 18:16:29 +0300 [thread overview]
Message-ID: <20140602151629.GA8160@node.dhcp.inet.fi> (raw)
In-Reply-To: <538CAA520200007800016E87@mail.emea.novell.com>
On Mon, Jun 02, 2014 at 03:46:10PM +0100, Jan Beulich wrote:
> For cold page allocations using the normal clear_highpage() mechanism
> may be inefficient on certain architectures, namely due to needlessly
> replacing a good part of the data cache contents. Introduce an arch-
> overridable clear_cold_highpage() (using streaming non-temporal stores
> on x86, where an override gets implemented right away) to make use of
> in this specific case.
>
> Leverage the impovement in the Xen balloon driver, eliminating the
> explicit scrub_page() function.
Any benchmark data?
I've tried non-temporal stores to clear huge pages, but it didn't helped
much. I believe it can vary between micro-architectures, but we need
numbers. I've played with Westmere that time.
--
Kirill A. Shutemov
--
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-06-02 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 14:46 [PATCH] improve __GFP_COLD/__GFP_ZERO interaction Jan Beulich
2014-06-02 15:16 ` Kirill A. Shutemov [this message]
2014-06-02 15:27 ` Jan Beulich
2014-06-02 15:49 ` Kirill A. Shutemov
2014-06-02 15:54 ` David Vrabel
2014-06-04 16:03 ` Jan Beulich
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=20140602151629.GA8160@node.dhcp.inet.fi \
--to=kirill@shutemov.name \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.