linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@amacapital.net>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Andy Lutomirski <luto@kernel.org>,
	Hugh Dickins <hughd@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: do not let vdso pages into LRU rotation
Date: Fri, 29 Jan 2016 14:21:23 -0800	[thread overview]
Message-ID: <CALCETrVLf5LeAhAhrcYFYAK3yS+3vdyoE5oG-epFvpkab5UykA@mail.gmail.com> (raw)
In-Reply-To: <20160128213302.GB4163@cmpxchg.org>

On Thu, Jan 28, 2016 at 1:33 PM, Johannes Weiner <hannes@cmpxchg.org> wrote:
> On Wed, Jan 27, 2016 at 12:32:16PM -0800, Andy Lutomirski wrote:
>> On Wed, Jan 27, 2016 at 11:39 AM, Johannes Weiner <hannes@cmpxchg.org> wrote:
>> > Could the VDSO be a VM_MIXEDMAP to keep the initial unmanaged pages
>> > out of the VM while allowing COW into regular anonymous pages?
>>
>> Probably.  What are its limitations?  We want ptrace to work on it,
>> and mprotect needs to work and allow COW.  access_process_vm should
>> probably work, too.
>
> Thanks, that's good to know.
>
> However, after looking at this a little longer, it appears this would
> need work in do_wp_page() to support non-page COW copying, then adding
> vm_ops->access and complicating ->fault in all VDSO implementations.
>
> And it looks like - at least theoretically - drivers can inject non-VM
> pages into the page tables as well (comment above insert_page())
>
> Given that this behavior has been around for a long time (the comment
> at the bottom of vm_normal_page is ancient), I'll probably go with a
> more conservative approach; add a comment to mark_page_accessed() and
> filter out non-VM pages in the function I'm going to call from it.

I just checked: in -tip, I'm creating a VM_PFNMAP (not VM_MIXEDMAP)
vma and faulting a RAM page (with struct page and all) in using
vm_insert_pfn.  Is that okay, or so I need to use VM_MIXEDMAP instead?

--Andy

--
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>

      reply	other threads:[~2016-01-29 22:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 19:39 Johannes Weiner
2016-01-27 20:32 ` Andy Lutomirski
2016-01-28 21:33   ` Johannes Weiner
2016-01-29 22:21     ` Andy Lutomirski [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=CALCETrVLf5LeAhAhrcYFYAK3yS+3vdyoE5oG-epFvpkab5UykA@mail.gmail.com \
    --to=luto@amacapital.net \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@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