From: Andrea Arcangeli <aarcange@redhat.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org
Subject: [LSF/MM ATTEND] 2016 userfaultfd/KSMscale/THP
Date: Fri, 29 Jan 2016 18:53:49 +0100 [thread overview]
Message-ID: <20160129175349.GL12228@redhat.com> (raw)
Hello,
I'd like to attend this year LSF/MM summit. Possible topics that I
would suggest are:
o the userfaultfd syscall has been merged upstream and it's feature
complete for KVM postcopy live migration (available in current
upstream QEMU).
The extension to provide the write tracking feature to userfaultfd
was planned from the start and an implementation has already been
posted. The current implementation works fine for simple cases but
it's not fully complete yet (no mmu notifier, THP not working
etc..). The API of the new ioctls for the write protection feature
should be finalized before this can be merged in -mm/upstream and
the summit would be a good opportunity to discuss it. By April I
expect a fully functional implementation of the new feature would
become available.
The topic to extend the userfaultfd syscalls to hugetlbfs has
already been proposed. I'm interested about following up that too
and not just to hugetlbfs but in general to extend it to more
filebacked vmas types.
o KSMscale: a change needed to reduce the worst case computational
complexity of KSM is pending. This is needed to avoid long (as in
seconds) CPU stalls in the rmap_walks (or alternatively the random
materialization of unmovable pages anywhere in the physical ranges
of supposedly movable memblocks and movable zones) on systems with
larges amount of RAM and/or with dense workloads like clear
containers. Perhaps by April this will already have been fully
sorted out online and the patch will be already upstream, in which
case this topic would be obsolete and should be skipped, but if not,
I'd be nice to discuss this too.
o TLB flushing reduction in the rmap_walks: Mel and Hugh started
various work in this area. Patches have been posted for a certain
number of cases but it'd be good if we could optimize things for
secondary MMUs (i.e. KVM MMU notifiers) too and for more cases.
Last but not the least I'm also very interested about following the
Huge Page (Huge Page as in Transparent Huge Pages I assume) Futures
topic already proposed.
Thanks and hope to see you soon!
Andrea
--
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 17:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160129175349.GL12228@redhat.com \
--to=aarcange@redhat.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).