From: Florian Weimer <fw@deneb.enyo.de>
To: Norbert Manthey <nmanthey@conp-solutions.com>
Cc: libc-alpha@sourceware.org, Siddhesh Poyarekar <siddhesh@sourceware.org>
Subject: Re: [[RFC][PATCH] v1 0/2] malloc/realloc with transparent huge page support
Date: Mon, 04 May 2020 06:36:08 +0200 [thread overview]
Message-ID: <87ftcgz58n.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20200503220708.2048246-1-nmanthey@conp-solutions.com> (Norbert Manthey's message of "Mon, 4 May 2020 00:07:06 +0200")
* Norbert Manthey:
> This change has been tested on top of glibc 2.23 in an Ubuntu 16.04
> environment for programs that benefit from huge pages due to their
> large memory usage and pseudo-random memory access patterns
> (e.g. SAT solvers, model checkers, optimization tools an
> others). More details on the performance improvements for these
> tools can be found in https://arxiv.org/abs/2004.14378, e.g. page 9.
Please show us the output of
$ cat /sys/kernel/mm/transparent_hugepage/enabled
from your test systems. Thanks.
In the paper, you say this:
| Because there might be applications running on the host that would
| suffer from larger pages, THP is usually disabled on physical
| systems and it is not advised to set the value to always.
However, the default value for Red Hat Enterprise Linux 7 is, in fact,
"always", so it is puzzling why you see such a large benefit for
long-running processes.
next prev parent reply other threads:[~2020-05-04 4:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 22:07 Norbert Manthey
2020-05-03 22:07 ` [[RFC][PATCH] v1 1/2] malloc: support transparent huge pages Norbert Manthey
2020-05-03 22:07 ` [[RFC][PATCH] v1 2/2] malloc: improve THP effectiveness Norbert Manthey
2020-05-03 22:21 ` Andrew Pinski
2020-05-03 22:15 ` [[RFC][PATCH] v1 0/2] malloc/realloc with transparent huge page support H.J. Lu
2020-05-04 4:36 ` Florian Weimer [this message]
2020-05-04 6:58 ` Norbert Manthey
2020-05-04 7:07 ` Florian Weimer
2020-05-04 21:07 ` DJ Delorie
2020-05-04 21:44 ` Norbert Manthey
[not found] <7bd30e6c-7ae8-4c03-a818-6309351b3df9@email.android.com>
2020-05-04 8:27 ` Florian Weimer
2020-05-04 13:31 ` Adhemerval Zanella
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=87ftcgz58n.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.org \
--cc=nmanthey@conp-solutions.com \
--cc=siddhesh@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).