From: Jerome Glisse <jglisse@redhat.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org,
Anshuman Khandual <khandual@linux.vnet.ibm.com>,
Balbir Singh <bsingharora@gmail.com>,
David Rientjes <rientjes@google.com>,
John Hubbard <jhubbard@nvidia.com>,
Michal Hocko <mhocko@suse.com>
Subject: [LSF/MM TOPIC] HMM status upstream user what's next, mmu_notifier
Date: Tue, 16 Jan 2018 16:30:08 -0500 [thread overview]
Message-ID: <20180116213008.GC8801@redhat.com> (raw)
I want to talk about status of HMM and respective upstream user for
it and also talk about what's next in term of features/improvement
plan (generic page write protection, mmu_notifier, ...). Most likely
short 15-30minutes if mmu_notifier is split into its own topic.
I want to talk about mmu_notifier, specificaly adding more context
information to mmu_notifier callback (why a notification is happening
reclaim, munmap, migrate, ...). Maybe we can grow this into its own
topic and talk about mmu_notifier and issue with it like OOM or being
able to sleep/take lock ... and improving mitigation.
People (mmu_notifier probably interest a larger set):
"Anshuman Khandual" <khandual@linux.vnet.ibm.com>
"Balbir Singh" <bsingharora@gmail.com>
"David Rientjes" <rientjes@google.com>
"John Hubbard" <jhubbard@nvidia.com>
"Michal Hocko" <mhocko@suse.com>
--
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 reply other threads:[~2018-01-16 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 21:30 Jerome Glisse [this message]
2018-01-17 1:19 ` [LSF/MM TOPIC] HMM status upstream user what's next, mmu_notifier Liubo(OS Lab)
2018-01-17 1:59 ` Figo.zhang
2018-01-17 2:05 ` Jerome Glisse
2018-01-25 15:37 ` Michal Hocko
2018-01-19 5:24 ` John Hubbard
2018-01-25 15:37 ` Michal Hocko
2018-02-14 9:15 ` Balbir Singh
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=20180116213008.GC8801@redhat.com \
--to=jglisse@redhat.com \
--cc=bsingharora@gmail.com \
--cc=jhubbard@nvidia.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mhocko@suse.com \
--cc=rientjes@google.com \
/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;
as well as URLs for NNTP newsgroup(s).