From: Mel Gorman <mgorman@techsingularity.net>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [LSF/MM ATTEND] MM track: NUMA, THP locality, reclaim
Date: Mon, 18 Feb 2019 14:32:03 +0000 [thread overview]
Message-ID: <20190218143203.GW9565@techsingularity.net> (raw)
Hi,
I would like to attend the MM track of LSF/MM if a slot is available. My
involvement in MM-specific topics tend to be a little sporadic given my
current role but I generally pop up for some page allocator, compaction,
NUMA, reclaim and THP topics in particular. Recent contributions have
been primarily compaction and fragmentation control related with a number
of patches queued up in Andrew's tree for 5.1-rc1 that finally seems to
have stopped generating bug reports.
I'm particularly interested in the following proposals in rough order
of interest;
o NUMA remote THP vs NUMA local non-THP under MADV_HUGEPAGE
o NUMA, memory hierarchy and device memory
o Memory reclaim with NUMA rebalancing
The other topics are interesting but these are the three I'm likely
to spend the most brain power on. At this time I'm not proposing a
topic. While I'm periodically kicking a compaction-related series around,
I don't expect it to be particularly controversial that would warrant a
discussion. That might change, particularly if it starts colliding with
"NUMA remote THP vs NUMA local non-THP under MADV_HUGEPAGE". If so, I'll
do a topic proposal later or beg/borrow/steal a lightening talk slot.
--
Mel Gorman
SUSE Labs
reply other threads:[~2019-02-18 14:32 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=20190218143203.GW9565@techsingularity.net \
--to=mgorman@techsingularity.net \
--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