All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nitin Gupta <ngupta@vflare.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Minchan Kim <minchan.kim@gmail.com>,
	gregkh@suse.de, Chris Mason <chris.mason@oracle.com>,
	akpm@linux-foundation.org, torvalds@linux-foundation.org,
	matthew@wil.cx, linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	jeremy@goop.org, Kurt Hackel <kurt.hackel@oracle.com>,
	npiggin@kernel.dk, riel@redhat.com,
	Konrad Wilk <konrad.wilk@oracle.com>,
	mel@csn.ul.ie, kosaki.motohiro@jp.fujitsu.com,
	sfr@canb.auug.org.au, wfg@mail.ustc.edu.cn, tytso@mit.edu,
	viro@zeniv.linux.org.uk, hughd@google.com, hannes@cmpxchg.org
Subject: Re: [PATCH V2 2/3] drivers/staging: zcache: host services and PAM services
Date: Wed, 09 Feb 2011 12:36:17 -0500	[thread overview]
Message-ID: <4D52D091.1000504@vflare.org> (raw)
In-Reply-To: <5c529b08-cf36-43c7-b368-f3f602faf358@default>

On 02/09/2011 11:39 AM, Dan Magenheimer wrote:
>
>
>> From: Minchan Kim [mailto:minchan.kim@gmail.com]
>
>> As I read your comment, I can't find the benefit of zram compared to
>> frontswap.
>
> Well, I am biased, but I agree that frontswap is a better technical
> solution than zram. ;-)  But "dynamic-ity" is very important to
> me and may be less important to others.
>


I agree that frontswap is better than zram when considering swap as the 
use case - no bio overhead, dynamic resizing. However, zram being a 
*generic* block-device has some unique cases too like hosting files on 
/tmp, various caches under /var or any place where a compressed 
in-memory block device can help.

So, frontswap and zram have overlapping use case of swap but are not the 
same.

Thanks,
Nitin

WARNING: multiple messages have this Message-ID (diff)
From: Nitin Gupta <ngupta@vflare.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Minchan Kim <minchan.kim@gmail.com>,
	gregkh@suse.de, Chris Mason <chris.mason@oracle.com>,
	akpm@linux-foundation.org, torvalds@linux-foundation.org,
	matthew@wil.cx, linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	jeremy@goop.org, Kurt Hackel <kurt.hackel@oracle.com>,
	npiggin@kernel.dk, riel@redhat.com,
	Konrad Wilk <konrad.wilk@oracle.com>,
	mel@csn.ul.ie, kosaki.motohiro@jp.fujitsu.com,
	sfr@canb.auug.org.au, wfg@mail.ustc.edu.cn, tytso@mit.edu,
	viro@zeniv.linux.org.uk, hughd@google.com, hannes@cmpxchg.org
Subject: Re: [PATCH V2 2/3] drivers/staging: zcache: host services and PAM services
Date: Wed, 09 Feb 2011 12:36:17 -0500	[thread overview]
Message-ID: <4D52D091.1000504@vflare.org> (raw)
In-Reply-To: <5c529b08-cf36-43c7-b368-f3f602faf358@default>

On 02/09/2011 11:39 AM, Dan Magenheimer wrote:
>
>
>> From: Minchan Kim [mailto:minchan.kim@gmail.com]
>
>> As I read your comment, I can't find the benefit of zram compared to
>> frontswap.
>
> Well, I am biased, but I agree that frontswap is a better technical
> solution than zram. ;-)  But "dynamic-ity" is very important to
> me and may be less important to others.
>


I agree that frontswap is better than zram when considering swap as the 
use case - no bio overhead, dynamic resizing. However, zram being a 
*generic* block-device has some unique cases too like hosting files on 
/tmp, various caches under /var or any place where a compressed 
in-memory block device can help.

So, frontswap and zram have overlapping use case of swap but are not the 
same.

Thanks,
Nitin

--
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>

  reply	other threads:[~2011-02-09 17:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07  3:26 [PATCH V2 2/3] drivers/staging: zcache: host services and PAM services Dan Magenheimer
2011-02-07  3:26 ` Dan Magenheimer
2011-02-08 22:48 ` Minchan Kim
2011-02-08 22:48   ` Minchan Kim
2011-02-08 23:27   ` Dan Magenheimer
2011-02-08 23:27     ` Dan Magenheimer
2011-02-08 23:56     ` Minchan Kim
2011-02-08 23:56       ` Minchan Kim
2011-02-09 16:39       ` Dan Magenheimer
2011-02-09 16:39         ` Dan Magenheimer
2011-02-09 17:36         ` Nitin Gupta [this message]
2011-02-09 17:36           ` Nitin Gupta
2011-02-09 23:46           ` Minchan Kim
2011-02-09 23:46             ` Minchan Kim
2011-02-10  1:17             ` Nitin Gupta
2011-02-10  1:17               ` Nitin Gupta
2011-02-09 23:57         ` Minchan Kim
2011-02-09 23:57           ` Minchan Kim
2011-02-09 23:58           ` Minchan Kim
2011-02-09 23:58             ` Minchan Kim
2011-02-15 16:53 ` Konrad Rzeszutek Wilk
2011-02-15 16:53   ` Konrad Rzeszutek Wilk
2011-02-15 17:25   ` Greg KH
2011-02-15 17:25     ` Greg KH
2011-02-15 18:18     ` Konrad Rzeszutek Wilk
2011-02-15 18:18       ` Konrad Rzeszutek Wilk

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=4D52D091.1000504@vflare.org \
    --to=ngupta@vflare.org \
    --cc=akpm@linux-foundation.org \
    --cc=chris.mason@oracle.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=gregkh@suse.de \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=kurt.hackel@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=matthew@wil.cx \
    --cc=mel@csn.ul.ie \
    --cc=minchan.kim@gmail.com \
    --cc=npiggin@kernel.dk \
    --cc=riel@redhat.com \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    --cc=wfg@mail.ustc.edu.cn \
    /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.