From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Robert Jennings <rcj@linux.vnet.ibm.com>, Bob Liu <bob.liu@oracle.com>
Cc: Seth Jennings <sjenning@linux.vnet.ibm.com>,
minchan@kernel.org, Nitin Gupta <nitingupta910@gmail.com>,
Konrad Wilk <konrad.wilk@oracle.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Bob Liu <lliubbo@gmail.com>,
Luigi Semenzato <semenzato@google.com>,
Mel Gorman <mgorman@suse.de>
Subject: RE: zsmalloc limitations and related topics
Date: Thu, 14 Mar 2013 11:54:35 -0700 (PDT) [thread overview]
Message-ID: <006139fe-542e-46f0-8b6c-b05efeb232d6@default> (raw)
In-Reply-To: <20130314132046.GA3172@linux.vnet.ibm.com>
> From: Robert Jennings [mailto:rcj@linux.vnet.ibm.com]
> Sent: Thursday, March 14, 2013 7:21 AM
> To: Bob
> Cc: Seth Jennings; Dan Magenheimer; minchan@kernel.org; Nitin Gupta; Konrad Wilk; linux-mm@kvack.org;
> linux-kernel@vger.kernel.org; Bob Liu; Luigi Semenzato; Mel Gorman
> Subject: Re: zsmalloc limitations and related topics
>
> * Bob (bob.liu@oracle.com) wrote:
> > On 03/14/2013 06:59 AM, Seth Jennings wrote:
> > >On 03/13/2013 03:02 PM, Dan Magenheimer wrote:
> > >>>From: Robert Jennings [mailto:rcj@linux.vnet.ibm.com]
> > >>>Subject: Re: zsmalloc limitations and related topics
> > >>
> <snip>
> > >>Yes. And add pageframe-reclaim to this list of things that
> > >>zsmalloc should do but currently cannot do.
> > >
> > >The real question is why is pageframe-reclaim a requirement? What
> > >operation needs this feature?
> > >
> > >AFAICT, the pageframe-reclaim requirements is derived from the
> > >assumption that some external control path should be able to tell
> > >zswap/zcache to evacuate a page, like the shrinker interface. But this
> > >introduces a new and complex problem in designing a policy that doesn't
> > >shrink the zpage pool so aggressively that it is useless.
> > >
> > >Unless there is another reason for this functionality I'm missing.
> > >
> >
> > Perhaps it's needed if the user want to enable/disable the memory
> > compression feature dynamically.
> > Eg, use it as a module instead of recompile the kernel or even
> > reboot the system.
It's worth thinking about: Under what circumstances would a user want
to turn off compression? While unloading a compression module should
certainly be allowed if it makes a user comfortable, in my opinion,
if a user wants to do that, we have done our job poorly (or there
is a bug).
> To unload zswap all that is needed is to perform writeback on the pages
> held in the cache, this can be done by extending the existing writeback
> code.
Actually, frontswap supports this directly. See frontswap_shrink.
--
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 prev parent reply other threads:[~2013-03-14 18:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 23:24 zsmalloc limitations and related topics Dan Magenheimer
2013-02-28 22:00 ` Dan Magenheimer
2013-03-01 1:40 ` Ric Mason
2013-03-04 18:29 ` Dan Magenheimer
2013-03-13 15:14 ` Robert Jennings
2013-03-13 15:33 ` Seth Jennings
2013-03-13 15:56 ` Seth Jennings
2013-03-13 20:02 ` Dan Magenheimer
2013-03-13 22:59 ` Seth Jennings
2013-03-14 12:02 ` Bob
2013-03-14 13:20 ` Robert Jennings
2013-03-14 18:54 ` Dan Magenheimer [this message]
2013-03-15 16:14 ` Seth Jennings
2013-03-15 16:54 ` Dan Magenheimer
2013-03-15 16:18 ` Seth Jennings
2013-03-14 17:39 ` Dan Magenheimer
2013-03-14 19:16 ` Dan Magenheimer
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=006139fe-542e-46f0-8b6c-b05efeb232d6@default \
--to=dan.magenheimer@oracle.com \
--cc=bob.liu@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lliubbo@gmail.com \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=nitingupta910@gmail.com \
--cc=rcj@linux.vnet.ibm.com \
--cc=semenzato@google.com \
--cc=sjenning@linux.vnet.ibm.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).