From: Minchan Kim <minchan@kernel.org>
To: Simon Jeons <simon.jeons@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
Nitin Gupta <ngupta@vflare.org>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Konrad Rzeszutek Wilk <konrad@darnok.org>
Subject: Re: [PATCH] zsmalloc: Add Kconfig for enabling PTE method
Date: Mon, 4 Feb 2013 11:58:41 +0900 [thread overview]
Message-ID: <20130204025841.GE2688@blaptop> (raw)
In-Reply-To: <1359943329.1590.0.camel@kernel.cn.ibm.com>
On Sun, Feb 03, 2013 at 08:02:09PM -0600, Simon Jeons wrote:
> On Mon, 2013-02-04 at 09:23 +0900, Minchan Kim wrote:
> > Zsmalloc has two methods 1) copy-based and 2) pte based to access
> > allocations that span two pages.
> > You can see history why we supported two approach from [1].
> >
> > But it was bad choice that adding hard coding to select architecture
> > which want to use pte based method. This patch removed it and adds
> > new Kconfig to select the approach.
> >
> > This patch is based on next-20130202.
>
> What's the meaning of 'zs' in zsmalloc? It's short for what?
I'm not right person to answer but I guess it stands for compressed slab.
--
Kind regards,
Minchan Kim
next prev parent reply other threads:[~2013-02-04 2:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 0:23 [PATCH] zsmalloc: Add Kconfig for enabling PTE method Minchan Kim
2013-02-04 2:02 ` Simon Jeons
2013-02-04 2:58 ` Minchan Kim [this message]
2013-02-04 18:51 ` Greg Kroah-Hartman
2013-02-05 0:08 ` Minchan Kim
2013-02-05 19:25 ` Greg Kroah-Hartman
2013-02-06 1:17 ` Minchan Kim
2013-02-06 1:42 ` Greg Kroah-Hartman
2013-02-06 1:44 ` Minchan Kim
2013-02-16 6:28 ` Ric Mason
2013-02-18 18:24 ` Seth Jennings
2013-02-18 23:48 ` 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=20130204025841.GE2688@blaptop \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dan.magenheimer@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ngupta@vflare.org \
--cc=simon.jeons@gmail.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).