From: Michel Lespinasse <walken@google.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Hugh Dickins <hughd@google.com>, linux-mm <linux-mm@kvack.org>
Subject: huge zero page vs FOLL_DUMP
Date: Fri, 11 Jan 2013 15:53:34 -0800 [thread overview]
Message-ID: <CANN689E5iw=UHfG1r82c91cZVqhX9xrxttKw3SCy=ZSgcAicNQ@mail.gmail.com> (raw)
Hi,
follow_page() has code to return ERR_PTR(-EFAULT) when it encounters
the zero page and FOLL_DUMP flag is passed - this is used to avoid
dumping the zero page to disk when doing core dumps, and also by
munlock to avoid having potentially large number of threads trying to
munlock the zero page at once, which we can't reclaim anyway.
We don't have the corresponding logic when follow_page() encounters a
huge zero page. I think we should, preferably before 3.8. However, I
am slightly confused as to what to do for the munlock case, as the
huge zero page actually does seem to be reclaimable. My guess is that
we could still skip the munlocks, until the zero page is actually
reclaimed at which point we should check if we can munlock it.
Kirill, is this something you would have time to look into ?
Thanks,
--
Michel "Walken" Lespinasse
A program is never fully debugged until the last user dies.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2013-01-11 23:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 23:53 Michel Lespinasse [this message]
2013-01-12 3:36 ` Kirill A. Shutemov
2013-01-12 4:27 ` Michel Lespinasse
2013-01-14 15:18 ` Kirill A. Shutemov
2013-01-13 1:43 ` Simon Jeons
2013-01-13 16:10 ` Kirill A. Shutemov
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='CANN689E5iw=UHfG1r82c91cZVqhX9xrxttKw3SCy=ZSgcAicNQ@mail.gmail.com' \
--to=walken@google.com \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox