linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas Aji <srinivas.aji@memverge.com>
To: David Hildenbrand <david@redhat.com>
Cc: linux-nvdimm <linux-nvdimm@lists.01.org>,
	Linux MM <linux-mm@kvack.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Vivek Goyal <vgoyal@redhat.com>,
	David Woodhouse <dwmw@amazon.com>,
	"Gowans, James" <jgowans@amazon.com>,
	Yue Li <yue.li@memverge.com>,
	Beau Beauchamp <beau.beauchamp@memverge.com>
Subject: Re: [RFC PATCH 0/4] Allow persistent data on DAX device being used as KMEM
Date: Wed, 3 Aug 2022 00:23:47 +0530	[thread overview]
Message-ID: <Yulyu3WXEyr1JPjF@memverge.com> (raw)
In-Reply-To: <5b5266fa-87e0-2db4-5da6-6f8f299c7cdb@redhat.com>

On Tue, Aug 02, 2022 at 08:03:10PM +0200, David Hildenbrand wrote:
> > Srinivas Aji (4):
> >   mm/memory_hotplug: Add MHP_ALLOCATE flag which treats hotplugged
> >     memory as allocated
> 
> Without seeing the actual patches, I am very skeptical that this is the
> right approach, especially regarding memory onlining/offlining.
> 
> virtio-mem achieves something similar (yet different) by hooking into
> generic_online_page(). From there, you can control what should actually
> happen with memory that is getting onlined (e.g., free them to the buddy
> or treat them differently).
> 
> Did you evaluate going that path?

Thanks for the feedback. I had not tried this. Let me see if what I am
trying here can be done using the online_page_callback mechanism.

Thanks,
Srinivas


  reply	other threads:[~2022-08-02 18:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02 17:57 Srinivas Aji
2022-08-02 18:02 ` [RFC PATCH 1/4] mm/memory_hotplug: Add MHP_ALLOCATE flag which treats hotplugged memory as allocated Srinivas Aji
2022-08-02 18:03 ` [RFC PATCH 0/4] Allow persistent data on DAX device being used as KMEM David Hildenbrand
2022-08-02 18:53   ` Srinivas Aji [this message]
2022-08-02 18:07 ` [RFC PATCH 2/4] device-dax: Add framework for keeping persistent data in DAX KMEM Srinivas Aji
2022-08-02 18:10 ` [RFC PATCH 3/4] device-dax: Add a NONE type for DAX KMEM persistence Srinivas Aji
2022-08-02 18:12 ` [RFC PATCH 4/4] device-dax: Add a block device persistent type, BLK, for DAX KMEM Srinivas Aji
2022-08-03 21:19   ` Fabio M. De Francesco
2022-08-05 12:46 ` [RFC PATCH 0/4] Allow persistent data on DAX device being used as KMEM David Hildenbrand
2022-08-08 21:21   ` Srinivas Aji
2022-08-08 23:05     ` Dan Williams

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=Yulyu3WXEyr1JPjF@memverge.com \
    --to=srinivas.aji@memverge.com \
    --cc=beau.beauchamp@memverge.com \
    --cc=dan.j.williams@intel.com \
    --cc=david@redhat.com \
    --cc=dwmw@amazon.com \
    --cc=jgowans@amazon.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=vgoyal@redhat.com \
    --cc=yue.li@memverge.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