From: Larry Bassel <lbassel@codeaurora.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Sameer Pramod Niphadkar <spniphadkar@gmail.com>,
Larry Bassel <lbassel@codeaurora.org>,
linux-mm@kvack.org, vgandhi@codeaurora.org,
Xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] Re: RFC -- new zone type
Date: Thu, 29 Sep 2011 10:00:21 -0700 [thread overview]
Message-ID: <20110929170021.GB7007@labbmf-linux.qualcomm.com> (raw)
In-Reply-To: <c2d9add1-0095-4319-8936-db1b156559bf@default>
On 29 Sep 11 09:38, Dan Magenheimer wrote:
> > From: Sameer Pramod Niphadkar [mailto:spniphadkar@gmail.com]
> > Sent: Thursday, September 29, 2011 12:08 AM
> > To: Larry Bassel
> > Cc: linux-mm@kvack.org; vgandhi@codeaurora.org; Xen-devel@lists.xensource.com
> > Subject: [Xen-devel] Re: RFC -- new zone type
> >
> > On Wed, Sep 28, 2011 at 11:39 PM, Larry Bassel <lbassel@codeaurora.org> wrote:
> > > We need to create a large (~100M) contiguous physical memory region
> > > which will only be needed occasionally. As this region will
> > > use up 10-20% of all of the available memory, we do not want
> > > to pre-reserve it at boot time. Instead, we want to create
> > > this memory region "on the fly" when asked to by userspace,
> > > and do it as quickly as possible, and return it to
> > > system use when not needed.
> > >
> > > AFAIK, this sort of operation is currently done using memory
> > > compaction (as CMA does for instance).
> > > Alternatively, this memory region (if it is in a fixed place)
> > > could be created using "logical memory hotremove" and returned
> > > to the system using "logical memory hotplug". In either case,
> > > the contiguous physical memory would be created via migrating
> > > pages from the "movable zone".
> > >
> > > The problem with this approach is that the copying of up to 25000
> > > pages may take considerable time (as well as finding destinations
> > > for all of the pages if free memory is scarce -- this may
> > > even fail, causing the memory region not to be created).
> > >
> > > It was suggested to me that a new zone type which would be similar
> > > to the "movable zone" but is only allowed to contain pages
> > > that can be discarded (such as text) could solve this problem,
> > > so that there is no copying or finding destination pages needed (thus
> > > considerably reducing latency).
>
> If I read the above correctly, you are talking about indeed
> pre-reserving your ~100MB contiguous chunk of memory but using
> it for "discardable" pages only, then discarding all of those
> pages when you need the memory region, then going back to using
> the contiguous chunk for discardable pages, and so on.
Yes, that is exactly what we want to do.
>
> You may be interested in the concept of "ephemeral pages"
> introduced by transcendent memory ("tmem") and the cleancache
> patchset which went upstream at 3.0. If you write a driver
> (called a "backend" in tmem language) that accepts pages
> from cleancache, you would be able to use your 100MB contiguous
> chunk of memory for clean pagecache pages when it is not needed
> for your other purposes, easily discard all the pages when
> you do need the space, then start using it for clean pagecache
> pages again when you don't need it for your purposes anymore
> (and repeat this cycle as many times as necessary).
>
> You maybe could call your driver "cleanzone".
>
> Zcache (also upstream in drivers/staging) does something like
> this already, though you might not want/need to use compression
> in your driver. In zcache, space reclaim is driven by the kernel
> "shrinker" code that runs when memory is low, but another trigger
> could easily be used. Also there is likely a lot of code in
> zcache (e.g. tmem.c) that you could leverage.
>
> For more info, see:
> http://lwn.net/Articles/454795/
> http://oss.oracle.com/projects/tmem
Thanks very much, I'll look into these.
>
> I'd be happy to answer any questions if you are still interested
> after you have read the above documentation.
>
> Thanks,
> Dan
Larry
>
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-09-29 17:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 18:09 Larry Bassel
2011-09-29 6:07 ` Sameer Pramod Niphadkar
2011-09-29 16:38 ` [Xen-devel] " Dan Magenheimer
2011-09-29 17:00 ` Larry Bassel [this message]
2011-10-05 16:56 ` Larry Bassel
2011-10-05 19:43 ` Dan Magenheimer
2011-10-06 23:03 ` Larry Bassel
2011-10-07 15:23 ` Dan Magenheimer
2011-10-07 16:01 ` Seth Jennings
2011-10-07 17:19 ` Larry Bassel
2011-10-12 22:20 ` Dan Magenheimer
2011-09-29 20:19 ` Andi Kleen
2011-09-30 17:01 ` Larry Bassel
[not found] <20110928180909.GA7007@labbmf-linux.qualcomm.comCAOFJiu1_HaboUMqtjowA2xKNmGviDE55GUV4OD1vN2hXUf4-kQ@mail.gmail.com>
[not found] ` <c2d9add1-0095-4319-8936-db1b156559bf@default20111005165643.GE7007@labbmf-linux.qualcomm.com>
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=20110929170021.GB7007@labbmf-linux.qualcomm.com \
--to=lbassel@codeaurora.org \
--cc=Xen-devel@lists.xensource.com \
--cc=dan.magenheimer@oracle.com \
--cc=linux-mm@kvack.org \
--cc=spniphadkar@gmail.com \
--cc=vgandhi@codeaurora.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