linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: "Verma, Vishal L" <vishal.l.verma@intel.com>,
	"Williams, Dan J" <dan.j.williams@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"Wu, Fengguang" <fengguang.wu@intel.com>,
	"Hansen, Dave" <dave.hansen@intel.com>,
	"Huang, Ying" <ying.huang@intel.com>
Subject: Re: [RFC] Memory Tiering
Date: Thu, 17 Oct 2019 19:34:47 +0200	[thread overview]
Message-ID: <34ae126d-002b-b773-96c9-a78f7ef671e9@redhat.com> (raw)
In-Reply-To: <655c9d239ee1be425571aa1d71c681314e20984a.camel@intel.com>

On 17.10.19 19:07, Verma, Vishal L wrote:
> 
> On Thu, 2019-10-17 at 07:17 -0700, Dave Hansen wrote:
>> On 10/17/19 1:07 AM, David Hildenbrand wrote:
>>> Very interesting topic. I heard similar demand from HPC folks
>>> (especially involving other memory types ("tiers")). There, I think
>>> you often want to let the application manage that. But of course, for
>>> many applications an automatic management might already be
>>> beneficial.
>>>
>>> Am I correct that you are using PMEM in this area along with
>>> ZONE_DEVICE and not by giving PMEM to the buddy (add_memory())?
>>
>> The PMEM starts out as ZONE_DEVICE, but we unbind it from its original
>> driver and bind it to this stub of a "driver": drivers/dax/kmem.c which
>> uses add_memory() on it.
>>
>> There's some nice tooling inside the daxctl component of ndctl to do all
>> the sysfs magic to make this happen.
>>
> Here is more info about the daxctl command in question:
> 
> https://pmem.io/ndctl/daxctl-reconfigure-device.html
> 

Thanks, yeah I saw the patches back then (I though they were by Pavel 
but they were actually by you :) ) to add the memory to the buddy (via 
add_memory()).

Will explore some more, thanks!

-- 

Thanks,

David / dhildenb


  reply	other threads:[~2019-10-17 17:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16 20:05 [RFC] Memory Tiering Dave Hansen
2019-10-17  8:07 ` David Hildenbrand
2019-10-17 14:17   ` Dave Hansen
2019-10-17 17:07     ` Verma, Vishal L
2019-10-17 17:34       ` David Hildenbrand [this message]
2019-10-23 23:11 ` Jonathan Adams
2019-10-24 16:33   ` Dave Hansen
2019-10-25  3:30     ` Huang, Ying
2019-10-24 17:06   ` Yang Shi
2019-10-25  3:40   ` Huang, Ying

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=34ae126d-002b-b773-96c9-a78f7ef671e9@redhat.com \
    --to=david@redhat.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@intel.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=vishal.l.verma@intel.com \
    --cc=ying.huang@intel.com \
    /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).