From: "D. Cooper Stevenson" <cooper@cooper.stevenson.name>
To: linux-kernel@vger.kernel.org
Subject: Non-linear Remap Vs. VM Cleanup: Performance Hit
Date: Tue, 24 Feb 2015 14:36:25 -0800 [thread overview]
Message-ID: <54ECFCE9.9030407@cooper.stevenson.name> (raw)
Hello All,
I read the Linus's release for RC1. One of his favorite features in the
release are, "actually some vm cleanups, where this release is getting
rid of the largely unused non-linear remapping code (replaced with just
emulating it with lots of smaller mappings) and unifies the NUMA and
PROTNONE handling for page tables."
I understand that non-linear page remapping is unused (and, presumably,
reduces the code base size) but according to the remap_file_pages man
page (http://man7.org/linux/man-pages/man2/remap_file_pages.2.html)
non-linear system will be, "eventually be replaced by a slower in-kernel
emulation."
Was this a change of necessity? What gives?
Also, would you please Cc: me on your replies as I am not a member of
the mailing list?
Best Regards,
-Cooper
next reply other threads:[~2015-02-25 6:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 22:36 D. Cooper Stevenson [this message]
2015-02-27 15:39 ` Non-linear Remap Vs. VM Cleanup: Performance Hit 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=54ECFCE9.9030407@cooper.stevenson.name \
--to=cooper@cooper.stevenson.name \
--cc=linux-kernel@vger.kernel.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