From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: "D. Cooper Stevenson" <cooper@cooper.stevenson.name>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Non-linear Remap Vs. VM Cleanup: Performance Hit
Date: Fri, 27 Feb 2015 17:39:05 +0200 [thread overview]
Message-ID: <20150227153905.GA12562@node.dhcp.inet.fi> (raw)
In-Reply-To: <54ECFCE9.9030407@cooper.stevenson.name>
On Tue, Feb 24, 2015 at 02:36:25PM -0800, D. Cooper Stevenson wrote:
> 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?
As with all cleanups it's not necessary, but it makes life easier.
It removed >1.5k lines of non-trivial code from critical path of the
kernel. It's rarely used and tend to be error-prone. And developers need
to be aware about exists of non-linear mapping while implementing new
features.
For instance, faultaround feature I've implemented was broken for
non-linear mapping for some time and it took time to track it down.
--
Kirill A. Shutemov
prev parent reply other threads:[~2015-02-27 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 22:36 Non-linear Remap Vs. VM Cleanup: Performance Hit D. Cooper Stevenson
2015-02-27 15:39 ` Kirill A. Shutemov [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=20150227153905.GA12562@node.dhcp.inet.fi \
--to=kirill@shutemov.name \
--cc=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