From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
linux-mm <linux-mm@kvack.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [RFC, PATCH 0/8] remap_file_pages() decommission
Date: Tue, 6 May 2014 14:51:24 -0700 [thread overview]
Message-ID: <CA+55aFwUO5ubckFFEF+R=yos-Qd3Br4Fy3-LpXL0bDWCmMhb6g@mail.gmail.com> (raw)
In-Reply-To: <20140506143542.1d4e5f41be58b3ad3543ffe3@linux-foundation.org>
On Tue, May 6, 2014 at 2:35 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Tue, 6 May 2014 17:37:24 +0300 "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com> wrote:
>
>> This patchset replaces the syscall with emulation which creates new VMA on
>> each remap and remove code to support non-linear mappings.
>>
>> Nonlinear mappings are pain to support and it seems there's no legitimate
>> use-cases nowadays since 64-bit systems are widely available.
>>
>> It's not yet ready to apply. Just to give rough idea of what can we get if
>> we'll deprecated remap_file_pages().
>>
>> I need to split patches properly and write correct commit messages. And there's
>> still code to remove.
>
> hah. That's bold. It would be great if we can get away with this.
>
> Do we have any feeling for who will be impacted by this and how badly?
I *would* love to get rid of the nonlinear mappings, but I really have
zero visibility into who ended up using it. I assume it's a "Oracle on
32-bit x86" kind of thing.
I think this is more of a distro question. Plus perhaps an early patch
to just add a warning first so that we can see who it triggers for?
Linus
--
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 prev parent reply other threads:[~2014-05-06 21:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 14:37 Kirill A. Shutemov
2014-05-06 14:37 ` [PATCH 1/8] mm: replace remap_file_pages() syscall with emulation Kirill A. Shutemov
2014-10-08 6:50 ` Vineet Gupta
2014-10-08 10:03 ` Kirill A. Shutemov
2014-05-06 14:37 ` [PATCH 2/8] mm: kill vm_operations_struct->remap_pages Kirill A. Shutemov
2014-05-19 15:03 ` Christoph Hellwig
2014-05-19 15:14 ` Kirill A. Shutemov
2014-05-06 14:37 ` [PATCH 3/8] mm: kill zap_details->nonlinear_vma Kirill A. Shutemov
2014-05-06 14:37 ` [PATCH 4/8] mm, rmap: kill rmap_walk_control->file_nonlinear() Kirill A. Shutemov
2014-05-06 14:37 ` [PATCH 5/8] mm, rmap: kill vma->shared.nonlinear Kirill A. Shutemov
2014-05-06 14:37 ` [PATCH 6/8] mm, rmap: kill mapping->i_mmap_nonlinear Kirill A. Shutemov
2014-05-06 14:37 ` [PATCH 7/8] mm: kill VM_NONLINEAR and FAULT_FLAG_NONLINEAR Kirill A. Shutemov
2014-05-06 14:37 ` [PATCH 8/8] mm, x86: kill pte_to_pgoff(), pgoff_to_pte() and pte_file*() Kirill A. Shutemov
2014-05-06 21:35 ` [RFC, PATCH 0/8] remap_file_pages() decommission Andrew Morton
2014-05-06 21:51 ` Linus Torvalds [this message]
2014-05-06 23:03 ` Kirill A. Shutemov
2014-05-06 23:28 ` Andrew Morton
2014-05-07 9:12 ` Peter Zijlstra
2014-05-07 16:46 ` Andrew Morton
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='CA+55aFwUO5ubckFFEF+R=yos-Qd3Br4Fy3-LpXL0bDWCmMhb6g@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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