From: Mike Kravetz <mike.kravetz@oracle.com>
To: David Frank <david_frank95@yahoo.com>,
Kernelnewbies <kernelnewbies@kernelnewbies.org>,
Linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: mmap with huge page
Date: Tue, 17 Jul 2018 16:56:53 -0700 [thread overview]
Message-ID: <3b40325e-a75e-017d-920e-83e090153621@oracle.com> (raw)
In-Reply-To: <115606142.5883850.1531854314452@mail.yahoo.com>
On 07/17/2018 12:05 PM, David Frank wrote:
> Hi,
> According to the instruction, I have to mount a huge directory to hugetlbfs and create file in the huge directory to use the mmap huge page feature. But the issue is that, the files in the huge directory takes up the huge pages configured through
> vm.nr_hugepages =
>
> even the files are not used.
>
> When the total size of the files in the huge directory = vm.nr_hugepages * huge page size, then mmap would fail with 'can not allocate memory' if the file to be mapped is in the huge dir or the call has HUGEPAGETLB flag.
>
> Basically, I have to move the files off of the huge directory to free up huge pages.
>
> Am I missing anything here?
>
No, that is working as designed.
hugetlbfs filesystems are generally pre-allocated with nr_hugepages
huge pages. That is the upper limit of huge pages available. You can
use overcommit/surplus pages to try and exceed the limit, but that
comes with a whole set of potential issues.
If you have not done so already, please see Documentation/vm/hugetlbpage.txt
in the kernel source tree.
--
Mike Kravetz
next parent reply other threads:[~2018-07-17 23:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <115606142.5883850.1531854314452.ref@mail.yahoo.com>
[not found] ` <115606142.5883850.1531854314452@mail.yahoo.com>
2018-07-17 23:56 ` Mike Kravetz [this message]
[not found] ` <1485529317.61381.1531872070328@mail.yahoo.com>
2018-07-18 10:37 ` mmap with huge page Michal Hocko
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=3b40325e-a75e-017d-920e-83e090153621@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=david_frank95@yahoo.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).