From: Rik van Riel <riel@redhat.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Nitin Gupta <ngupta@vflare.org>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
lliubbo@gmail.com, jmarchan@redhat.com, mgorman@suse.de,
hughd@google.com, akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: zsmalloc: Ensure handle is never 0 on success
Date: Thu, 07 Nov 2013 12:10:35 -0500 [thread overview]
Message-ID: <527BC98B.5060701@redhat.com> (raw)
In-Reply-To: <20131107070451.GA10645@bbox>
On 11/07/2013 02:04 AM, Minchan Kim wrote:
> I'm guilty and I have been busy by other stuff. Sorry for that.
> Fortunately, I discussed this issue with Hugh in this Linuxcon for a
> long time(Thanks Hugh!) he felt zram's block device abstraction is
> better design rather than frontswap backend stuff although it's a question
> where we put zsmalloc. I will CC Hugh because many of things is related
> to swap subsystem and his opinion is really important.
> And I discussed it with Rik and he feel positive about zram.
To clarify that, I agree with Minchan that there are certain
workloads where zram is probably more appropriate than zswap.
For most of the workloads that I am interested in, zswap will
be more interesting, but zram seems to have its own niche, and
I certainly do not want to hold back the embedded folks...
--
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: Rik van Riel <riel@redhat.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Nitin Gupta <ngupta@vflare.org>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
lliubbo@gmail.com, jmarchan@redhat.com, mgorman@suse.de,
hughd@google.com, akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: zsmalloc: Ensure handle is never 0 on success
Date: Thu, 07 Nov 2013 12:10:35 -0500 [thread overview]
Message-ID: <527BC98B.5060701@redhat.com> (raw)
In-Reply-To: <20131107070451.GA10645@bbox>
On 11/07/2013 02:04 AM, Minchan Kim wrote:
> I'm guilty and I have been busy by other stuff. Sorry for that.
> Fortunately, I discussed this issue with Hugh in this Linuxcon for a
> long time(Thanks Hugh!) he felt zram's block device abstraction is
> better design rather than frontswap backend stuff although it's a question
> where we put zsmalloc. I will CC Hugh because many of things is related
> to swap subsystem and his opinion is really important.
> And I discussed it with Rik and he feel positive about zram.
To clarify that, I agree with Minchan that there are certain
workloads where zram is probably more appropriate than zswap.
For most of the workloads that I am interested in, zswap will
be more interesting, but zram seems to have its own niche, and
I certainly do not want to hold back the embedded folks...
next prev parent reply other threads:[~2013-11-07 17:12 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 7:04 [PATCH] staging: zsmalloc: Ensure handle is never 0 on success Minchan Kim
2013-11-07 7:04 ` Minchan Kim
2013-11-07 17:06 ` Luigi Semenzato
2013-11-07 17:06 ` Luigi Semenzato
2013-11-07 17:36 ` Luigi Semenzato
2013-11-07 17:36 ` Luigi Semenzato
2013-11-08 2:02 ` Greg KH
2013-11-08 2:02 ` Greg KH
2013-11-07 17:10 ` Rik van Riel [this message]
2013-11-07 17:10 ` Rik van Riel
2013-11-08 10:44 ` Bob Liu
2013-11-08 10:44 ` Bob Liu
2013-11-12 15:41 ` Minchan Kim
2013-11-12 15:41 ` Minchan Kim
2013-11-13 2:42 ` Greg KH
2013-11-13 2:42 ` Greg KH
2013-11-13 6:24 ` Nitin Gupta
2013-11-13 6:24 ` Nitin Gupta
2013-11-14 4:00 ` Hugh Dickins
2013-11-14 4:00 ` Hugh Dickins
2013-11-14 16:21 ` Seth Jennings
2013-11-14 16:21 ` Seth Jennings
2013-11-15 0:47 ` Bob Liu
2013-11-15 0:47 ` Bob Liu
2013-11-15 0:31 ` Minchan Kim
2013-11-15 0:31 ` Minchan Kim
-- strict thread matches above, loose matches on Subject: below --
2013-11-06 0:54 Olav Haugan
2013-11-06 1:17 ` David Cohen
2013-11-06 20:56 ` Nitin Gupta
2013-11-06 23:46 ` Olav Haugan
2013-11-06 1:56 ` Greg KH
2013-11-06 21:09 ` Nitin Gupta
2013-11-06 22:10 ` Greg KH
2013-11-06 23:46 ` Nitin Gupta
2013-11-07 3:05 ` Greg KH
2013-11-07 0:00 ` Olav Haugan
2013-11-07 3:06 ` Greg KH
2013-11-07 22:57 ` Olav Haugan
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=527BC98B.5060701@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=hughd@google.com \
--cc=jmarchan@redhat.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=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 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.