From: Michal Hocko <mhocko@kernel.org>
To: David Frank <david_frank95@yahoo.com>
Cc: Kernelnewbies <kernelnewbies@kernelnewbies.org>,
Linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Mike Kravetz <mike.kravetz@oracle.com>
Subject: Re: mmap with huge page
Date: Wed, 18 Jul 2018 12:37:09 +0200 [thread overview]
Message-ID: <20180718103709.GB1431@dhcp22.suse.cz> (raw)
In-Reply-To: <1485529317.61381.1531872070328@mail.yahoo.com>
On Wed 18-07-18 00:01:10, David Frank wrote:
> Thanks Mike. I read the doc, which is not explicit on the non used file taking up huge page count
What do you consider non user file? The file contains a data somebody
might want to read later. You cannot simply remove it. This is not
different to any other in memory filesystem (e.g. tmpfs, ramfs)
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2018-07-18 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <115606142.5883850.1531854314452.ref@mail.yahoo.com>
2018-07-17 19:05 ` David Frank
2018-07-17 23:56 ` Mike Kravetz
2018-07-18 0:01 ` David Frank
2018-07-18 10:37 ` Michal Hocko [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=20180718103709.GB1431@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=david_frank95@yahoo.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
/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