From: "Bridgman, John" <John.Bridgman@amd.com>
To: James Hartshorn <jhartshorn@connexity.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Can we disable transparent hugepages for lack of a legitimate use case please?
Date: Mon, 24 Aug 2015 20:20:01 +0000 [thread overview]
Message-ID: <20150824201952.5931089.66204.70511@amd.com> (raw)
In-Reply-To: <BLUPR02MB1698DD8F0D1550366489DF8CCD620@BLUPR02MB1698.namprd02.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]
We find it useful for GPU compute applications (APU I suppose, with GPU access via IOMMUv2) working on large datasets.
I wouldn't have expected THP to find much use for databases -- those seem to be more like graphics stacks where you have enough hints about future usage to justify explicit management of pages. I thought of THP as "the solution for everything else".
From: James Hartshorn
Sent: Monday, August 24, 2015 3:12 PM
To: linux-mm@kvack.org
Subject: Can we disable transparent hugepages for lack of a legitimate use case please?
Hi,
I've been struggling with transparent hugepage performance issues, and can't seem to find anyone who actually uses it intentionally. Virtually every database that runs on linux however recommends disabling it or setting it to madvise. I'm referring to:
/sys/kernel/mm/transparent_hugepage/enabled
I asked on the internet http://unix.stackexchange.com/questions/201906/does-anyone-actually-use-and-benefit-from-transparent-huge-pages and got no responses there.
Independently I noticed
"sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case. If you have one, please send an email to linux-mm@kvack.org."
And thought wow that's exactly what should be done to transparent hugepages.
Thoughts?
[-- Attachment #2: Type: text/html, Size: 3894 bytes --]
next prev parent reply other threads:[~2015-08-24 20:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 20:12 Can we disable transparent hugepages for lack of a legitimate use case please? James Hartshorn
2015-08-24 20:20 ` Bridgman, John [this message]
2015-08-24 20:46 ` James Hartshorn
2015-08-24 23:20 ` Theodore Ts'o
2015-09-10 16:45 ` Andrea Arcangeli
2015-09-10 17:02 ` Andres Freund
2015-09-14 12:37 ` Vlastimil Babka
2015-08-25 9:25 ` Konstantin Khlebnikov
2015-08-25 9:56 ` Vlastimil Babka
2015-09-01 22:26 ` David Rientjes
2015-09-02 8:55 ` Konstantin Khlebnikov
2015-09-02 9:06 ` Vlastimil Babka
2015-09-09 22:05 ` Andrea Arcangeli
2015-09-03 19:33 ` Andi Kleen
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=20150824201952.5931089.66204.70511@amd.com \
--to=john.bridgman@amd.com \
--cc=jhartshorn@connexity.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 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.