linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Linux Memory Management List <linux-mm@kvack.org>,
	"lsf-pc@lists.linux-foundation.org"
	<lsf-pc@lists.linux-foundation.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
	Minchan Kim <minchan@kernel.org>,
	Jerome Glisse <jglisse@redhat.com>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	Balbir Singh <bsingharora@gmail.com>,
	Dave Hansen <dave.hansen@intel.com>,
	Michal Hocko <mhocko@suse.com>
Subject: [LSF/MM ATTEND] CDM, HMM, ZONE_DEVICE, Device Memory Infrastructure, Page Allocator, CMA
Date: Mon, 16 Jan 2017 19:05:20 +0530	[thread overview]
Message-ID: <8954f383-2a25-f89d-e6db-aa7bc12564bd@linux.vnet.ibm.com> (raw)

Hello,

I have been working on a coherent device memory (CDM) representation in
the kernel. Last year, I had posted these two RFCs in this regard which
attempts to represent non-system RAM coherent device memory as a NUMA
node with some allocation restrictions.

https://lkml.org/lkml/2016/10/24/19  (CDM with modified zonelists)
https://lkml.org/lkml/2016/11/22/339 (CDM with modified cpusets)

During the course of this work, I had experimented with existing device
memory frameworks like ZONE_DEVICE, HMM etc. In my quest for isolation,
also looked into how early system boot allocated CMA region can be used
in this regard. Thought I would like to participate primarily on the
device memory management infrastructure discussions (detailed TOPICs
list can be found below) but would also like to contribute in those
areas where I had faced some limitations or the other during the CDM
work.

I would like to attend to discuss on the listed topics on the mailing
list as mentioned below which I have already replied in their respective
threads as well.

(1) [LSF/MM TOPIC/ATTEND] Memory Types
(2) [LSF/MM TOPIC] Un-addressable device memory and block/fs implications
(3) [LSF/MM TOPIC] Memory hotplug, ZONE_DEVICE, and the future of struct page
(4) [LSF/MM ATTEND] HMM, CDM and other infrastructure for device memory management

Apart from this, would like to discuss on the following generic topics
as I had mentioned earlier.

(1) Support for memory hotplug as CMA regions
(2) Seamless migration between LRU pages and device managed non LRU CMA pages
(3) Explore the possibility of enforcing CDM node isolation through a changed
    buddy page allocator specifically how it currently handles requested
    nodemask_t along with cpuset based nodemask at various phases of fast path
    and slow path

Regards
Anshuman



--
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:[~2017-01-16 13:35 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=8954f383-2a25-f89d-e6db-aa7bc12564bd@linux.vnet.ibm.com \
    --to=khandual@linux.vnet.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=bsingharora@gmail.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@intel.com \
    --cc=jglisse@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=mhocko@suse.com \
    --cc=minchan@kernel.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