From: Balbir Singh <bsingharora@gmail.com>
To: lsf-pc <lsf-pc@lists.linux-foundation.org>
Cc: linux-mm <linux-mm@kvack.org>
Subject: [LSF/MM ATTEND] Attend mm summit 2018
Date: Thu, 22 Feb 2018 13:54:46 +1100 [thread overview]
Message-ID: <CAKTCnz=rS14Ry7pOC2qiX5wEbRZCKwP_0u7_ncanoV18Gz9=AQ@mail.gmail.com> (raw)
I did not send out an official request to attend earlier, but I was
invited by Jerome to attend. I was traveling for a big part of Jan and
some part of Feb 2018 and hence the delay in sending out this email
with my desire to attend
I did a proposal last year for N_COHERENT_MEMORY, but there was
suggestions that for coherent memory we do ZONE_DEVICE and thus
HMM/CDM came into the picture. I have good knowledge of the memory
cgroups subsystem and have been looking at HMM and HMM/CDM for over a
year now and playing with ZONE_DEVICE in general. I would like to
attend to learn and discuss on the following topics
1. HMM and HMM-CDM and arguments for whether NUMA makes sense or not.
Experiences gained with both technologies.
2. Memory cgroups - I don't see a pressing need for many new features,
but I'd like to see if we can revive some old proposals around virtual
memory limits
Balbir Singh.
--
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-02-22 2:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 2:54 Balbir Singh [this message]
2018-02-22 13:03 ` Michal Hocko
2018-02-22 13:23 ` Balbir Singh
2018-02-22 13:34 ` [Lsf-pc] " Michal Hocko
2018-02-22 22:01 ` virtual memory limits control (was Re: [Lsf-pc] [LSF/MM ATTEND] Attend mm summit 2018) Balbir Singh
2018-02-23 7:42 ` Michal Hocko
2018-02-25 23:08 ` 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='CAKTCnz=rS14Ry7pOC2qiX5wEbRZCKwP_0u7_ncanoV18Gz9=AQ@mail.gmail.com' \
--to=bsingharora@gmail.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