From: Seth Jennings <sjenning@linux.vnet.ibm.com>
To: Bob Liu <lliubbo@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
eternaleye@gmail.com, minchan@kernel.org, mgorman@suse.de,
gregkh@linuxfoundation.org, akpm@linux-foundation.org,
axboe@kernel.dk, ngupta@vflare.org, semenzato@google.com,
penberg@iki.fi, sonnyrao@google.com, smbarber@google.com,
konrad.wilk@oracle.com, riel@redhat.com, kmpark@infradead.org,
Bob Liu <bob.liu@oracle.com>
Subject: Re: [PATCH 3/4] mm: zswap: add supporting for zsmalloc
Date: Mon, 19 Aug 2013 11:59:48 -0500 [thread overview]
Message-ID: <20130819165948.GA5703@variantweb.net> (raw)
In-Reply-To: <1376815249-6611-4-git-send-email-bob.liu@oracle.com>
On Sun, Aug 18, 2013 at 04:40:48PM +0800, Bob Liu wrote:
> Make zswap can use zsmalloc as its allocater.
> But note that zsmalloc don't reclaim any zswap pool pages mandatory, if zswap
> pool gets full, frontswap_store will be refused unless frontswap_get happened
> and freed some space.
>
> The reason of don't implement reclaiming zsmalloc pages from zswap pool is there
> is no requiremnet currently.
> If we want to do mandatory reclaim, we have to write those pages to real backend
> swap devices. But most of current users of zsmalloc are from embeded world,
> there is even no real backend swap device.
> This action is also the same as privous zram!
>
> For several area, zsmalloc has unpredictable performance characteristics when
> reclaiming a single page, then CONFIG_ZBUD are suggested.
Looking at this patch on its own, it does show how simple it could be
for zswap to support zsmalloc. So thanks!
However, I don't like all the ifdefs scattered everywhere. I'd like to
have a ops structure (e.g. struct zswap_alloc_ops) instead and just
switch ops based on the CONFIG flag. Or better yet, have it boot-time
selectable instead of build-time.
Seth
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Seth Jennings <sjenning@linux.vnet.ibm.com>
To: Bob Liu <lliubbo@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
eternaleye@gmail.com, minchan@kernel.org, mgorman@suse.de,
gregkh@linuxfoundation.org, akpm@linux-foundation.org,
axboe@kernel.dk, ngupta@vflare.org, semenzato@google.com,
penberg@iki.fi, sonnyrao@google.com, smbarber@google.com,
konrad.wilk@oracle.com, riel@redhat.com, kmpark@infradead.org,
Bob Liu <bob.liu@oracle.com>
Subject: Re: [PATCH 3/4] mm: zswap: add supporting for zsmalloc
Date: Mon, 19 Aug 2013 11:59:48 -0500 [thread overview]
Message-ID: <20130819165948.GA5703@variantweb.net> (raw)
In-Reply-To: <1376815249-6611-4-git-send-email-bob.liu@oracle.com>
On Sun, Aug 18, 2013 at 04:40:48PM +0800, Bob Liu wrote:
> Make zswap can use zsmalloc as its allocater.
> But note that zsmalloc don't reclaim any zswap pool pages mandatory, if zswap
> pool gets full, frontswap_store will be refused unless frontswap_get happened
> and freed some space.
>
> The reason of don't implement reclaiming zsmalloc pages from zswap pool is there
> is no requiremnet currently.
> If we want to do mandatory reclaim, we have to write those pages to real backend
> swap devices. But most of current users of zsmalloc are from embeded world,
> there is even no real backend swap device.
> This action is also the same as privous zram!
>
> For several area, zsmalloc has unpredictable performance characteristics when
> reclaiming a single page, then CONFIG_ZBUD are suggested.
Looking at this patch on its own, it does show how simple it could be
for zswap to support zsmalloc. So thanks!
However, I don't like all the ifdefs scattered everywhere. I'd like to
have a ops structure (e.g. struct zswap_alloc_ops) instead and just
switch ops based on the CONFIG flag. Or better yet, have it boot-time
selectable instead of build-time.
Seth
next prev parent reply other threads:[~2013-08-19 17:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-18 8:40 [PATCH 0/4] mm: merge zram into zswap Bob Liu
2013-08-18 8:40 ` Bob Liu
2013-08-18 8:40 ` [PATCH 1/4] drivers: staging: drop zram and zsmalloc Bob Liu
2013-08-18 8:40 ` Bob Liu
2013-08-18 8:40 ` [PATCH 2/4] mm: promote zsmalloc to mm/ Bob Liu
2013-08-18 8:40 ` Bob Liu
2013-08-18 8:40 ` [PATCH 3/4] mm: zswap: add supporting for zsmalloc Bob Liu
2013-08-18 8:40 ` Bob Liu
2013-08-19 16:59 ` Seth Jennings [this message]
2013-08-19 16:59 ` Seth Jennings
2013-08-20 1:11 ` Bob Liu
2013-08-20 1:11 ` Bob Liu
2013-08-18 8:40 ` [PATCH 4/4] mm: zswap: create a pseudo device /dev/zram0 Bob Liu
2013-08-18 8:40 ` Bob Liu
2013-08-19 17:46 ` Seth Jennings
2013-08-19 17:46 ` Seth Jennings
2013-08-20 2:03 ` Bob Liu
2013-08-20 2:03 ` Bob Liu
2013-08-19 4:10 ` [PATCH 0/4] mm: merge zram into zswap Minchan Kim
2013-08-19 4:10 ` Minchan Kim
2013-08-19 4:32 ` Bob Liu
2013-08-19 4:32 ` Bob Liu
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=20130819165948.GA5703@variantweb.net \
--to=sjenning@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bob.liu@oracle.com \
--cc=eternaleye@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kmpark@infradead.org \
--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=ngupta@vflare.org \
--cc=penberg@iki.fi \
--cc=riel@redhat.com \
--cc=semenzato@google.com \
--cc=smbarber@google.com \
--cc=sonnyrao@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.