From: Mike Kravetz <mike.kravetz@oracle.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [LSF/MM ATTEND] MM track: contig allocation, thp numa, userfaultfd
Date: Fri, 22 Feb 2019 14:22:03 -0800 [thread overview]
Message-ID: <a47b26e8-0048-e360-1f69-a296acf222f5@oracle.com> (raw)
If there is space available, I would like to attend the MM track of LSF/MM
this year. This is a somewhat lame request as I have not proposed a topic,
and my mm contributions this past year have been somewhat limited to finding
and fixing bugs hugetlbfs.
Topics in which I am interested and could contribute:
- Contiguous memory allocation. This seems to be an ongoing feature
request. John Hubbard wants a reliable and efficient method to
obtain provide huge pages. Zi Yan has put out a bunch of code to
support an alternate approach.
- THP and huge pages in general.
- Specific interest in Andrea's NUMA remote THP vs NUMA local non-THP
under MADV_HUGEPAGE proposal.
- Userfaultfd and Peter Xu approach to write protect support.
--
Mike Kravetz
reply other threads:[~2019-02-22 22:22 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=a47b26e8-0048-e360-1f69-a296acf222f5@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®