From: riel@surriel.com (Rik van Riel)
To: kernelnewbies@lists.kernelnewbies.org
Subject: HugePage by default
Date: Thu, 31 Jul 2014 00:06:04 -0400 [thread overview]
Message-ID: <53D9C0AC.7020708@surriel.com> (raw)
In-Reply-To: <CA+JLOiuFhsnnOcZr1pjMnSSqsr5MfkqUh=NdGsQui1tOmJXEOA@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/30/2014 04:06 PM, Xin Tong wrote:
> I see 2 ways to do this.
>
> 1. allocate 512 4KB contiguous pages everytime a handle_mm_fault is
> called and have the THP kernel thread to coalesce it to a huge
> page. 2. modify the kernel (maybe extensively) to allocate 2MB
> page by default.
>
> I like 1. better because it requires less modifications. but it is
> not as reliable. any suggestions
The kernel already does both of the above when
CONFIG_TRANSPARENT_HUGEPAGE=y
CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y
- --
All rights reversed.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJT2cCrAAoJEM553pKExN6DAFEH/2K7GdK21t+sEB8rletBkyX7
88xGjdvmtFqN1eJI/kcoq+xDyTSfH0+/C/NoXggnxDNOw0yEmKo9rarFaazlaVXH
/pPS+jxkuislTsIzhLpLXJH0o8fi742ZCYU4OAXCJ4ZPiFxo0I8gJGWzsjvsbcqa
fY6eDAdB2Zn70ABHLlp5iiEbVGf32L5OnwrtXDZTJqlX2GNZxmtBlYn4dr7Pzfl/
eio6u9JXk98ECKKKoHme/PFVSrpjUiOB8gzMDocs1bAuVSJGD36htH3HyI27lM5V
ruSM9dvQZe0XupELT5Xvu1IP0lmAXacKu/FvAZbVg1+3m1nYjLqdd+vONMkOmCE=
=6i2v
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2014-07-31 4:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 19:41 HugePage by default Xin Tong
2014-07-30 19:57 ` Valdis.Kletnieks at vt.edu
2014-07-30 20:06 ` Xin Tong
2014-07-30 22:22 ` Valdis.Kletnieks at vt.edu
2014-07-30 23:26 ` Xin Tong
2014-07-31 0:26 ` Valdis.Kletnieks at vt.edu
2014-07-31 0:49 ` Xin Tong
2014-07-31 0:53 ` Xin Tong
2014-07-31 4:06 ` Rik van Riel [this message]
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=53D9C0AC.7020708@surriel.com \
--to=riel@surriel.com \
--cc=kernelnewbies@lists.kernelnewbies.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 NNTP newsgroup(s).