From: Michel Lespinasse <walken@google.com>
To: Hugh Dickins <hughd@google.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Peter Zijlstra <peterz@infradead.org>,
Nick Piggin <npiggin@kernel.dk>,
Arjan van de Ven <arjan@infradead.org>,
linux-mm <linux-mm@kvack.org>,
Andrea Arcangeli <aarcange@redhat.com>
Subject: Re: RFC: reviving mlock isolation dead code
Date: Thu, 18 Nov 2010 03:16:02 -0800 [thread overview]
Message-ID: <AANLkTi=qSv2JnrAD7YWv+odPfirxq9Z8+Z2_FNAQtK8D@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.00.1011161444200.16422@tigran.mtv.corp.google.com>
On Tue, Nov 16, 2010 at 3:28 PM, Hugh Dickins <hughd@google.com> wrote:
> Yes, in fact, is anything required beyond Peter's original simple patch?
I initially thought there would be a problem with breaking COW on anon
pages (think of fork() + mlock() ), but then I realized these won't
show up in VM_SHARED vmas, so Peter's patch seems fine.
> Added Ccs of those most likely to agree or disagree with us.
I forgot to add Arjan and Andrea in my proposal ('Avoid dirtying pages
during mlock'). Let's move the discussion there.
--
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2010-11-18 11:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 10:16 Michel Lespinasse
2010-10-30 12:48 ` Michel Lespinasse
2010-11-01 7:05 ` KOSAKI Motohiro
2010-11-09 4:34 ` KOSAKI Motohiro
2010-11-10 12:21 ` Michel Lespinasse
2010-11-14 5:07 ` KOSAKI Motohiro
2010-11-16 1:44 ` Hugh Dickins
2010-11-16 6:50 ` Michel Lespinasse
2010-11-16 23:28 ` Hugh Dickins
2010-11-18 11:16 ` Michel Lespinasse [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='AANLkTi=qSv2JnrAD7YWv+odPfirxq9Z8+Z2_FNAQtK8D@mail.gmail.com' \
--to=walken@google.com \
--cc=aarcange@redhat.com \
--cc=arjan@infradead.org \
--cc=hughd@google.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@kernel.dk \
--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