From: Minchan Kim <minchan@kernel.org>
To: Nitin Gupta <ngupta@vflare.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 3/6] zsmalloc: rename zspage_order with zspage_pages
Date: Thu, 26 Apr 2012 10:46:52 +0900 [thread overview]
Message-ID: <4F98A90C.9020705@kernel.org> (raw)
In-Reply-To: <4F97F634.1010400@vflare.org>
On 04/25/2012 10:03 PM, Nitin Gupta wrote:
> On 04/25/2012 02:23 AM, Minchan Kim wrote:
>
>> zspage_order defines how many pages are needed to make a zspage.
>> So _order_ is rather awkward naming. It already deceive Jonathan
>> - http://lwn.net/Articles/477067/
>> " For each size, the code calculates an optimum number of pages (up to 16)"
>>
>> Let's change from _order_ to _pages_.
>>
>> Signed-off-by: Minchan Kim <minchan@kernel.org>
>> ---
>> drivers/staging/zsmalloc/zsmalloc-main.c | 14 +++++++-------
>> drivers/staging/zsmalloc/zsmalloc_int.h | 2 +-
>> 2 files changed, 8 insertions(+), 8 deletions(-)
>>
>
>
> Recently, Seth changed max_zspage_order to ZS_MAX_PAGES_PER_ZSPAGE for
> the same reason. I think it would be better to rename the function in a
> similary way to have some consistency. So, we could use:
>
> 1) get_pages_per_zspage() instead of get_zspage_pages()
> 2) class->pages_per_zspage instead of class->zspage_pages
>
No problem. Will do.
--
Kind regards,
Minchan Kim
next prev parent reply other threads:[~2012-04-26 1:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 6:23 [PATCH 0/6] zsmalloc: clean up and fix arch dependency Minchan Kim
2012-04-25 6:23 ` [PATCH 1/6] zsmalloc: use PageFlag macro instead of [set|test]_bit Minchan Kim
2012-04-25 12:43 ` Nitin Gupta
2012-04-25 6:23 ` [PATCH 2/6] zsmalloc: remove unnecessary alignment Minchan Kim
2012-04-25 12:53 ` Nitin Gupta
2012-04-26 1:42 ` Minchan Kim
2012-05-03 5:16 ` Nitin Gupta
2012-04-25 6:23 ` [PATCH 3/6] zsmalloc: rename zspage_order with zspage_pages Minchan Kim
2012-04-25 13:03 ` Nitin Gupta
2012-04-26 1:46 ` Minchan Kim [this message]
2012-04-25 6:23 ` [PATCH 4/6] zsmalloc: add/fix function comment Minchan Kim
2012-04-25 13:27 ` Nitin Gupta
2012-04-26 1:51 ` Minchan Kim
2012-04-25 6:23 ` [PATCH 5/6] zsmalloc: remove unnecessary type casting Minchan Kim
2012-04-25 13:35 ` Nitin Gupta
2012-04-25 17:56 ` Greg Kroah-Hartman
2012-04-25 18:13 ` Nitin Gupta
2012-04-26 1:58 ` Minchan Kim
2012-04-25 6:23 ` [PATCH 6/6] zsmalloc: make zsmalloc portable Minchan Kim
2012-04-25 14:32 ` Nitin Gupta
2012-04-25 15:40 ` Dan Magenheimer
2012-04-26 2:03 ` Minchan Kim
2012-04-26 5:07 ` Minchan Kim
2012-04-30 16:24 ` Seth Jennings
2012-04-25 16:37 ` Seth Jennings
2012-04-26 2:04 ` Minchan Kim
2012-05-07 15:14 ` Seth Jennings
2012-05-08 0:46 ` Minchan Kim
2012-04-26 2:11 ` Minchan Kim
2012-04-25 12:41 ` [PATCH 0/6] zsmalloc: clean up and fix arch dependency Nitin Gupta
2012-04-26 1:20 ` Minchan Kim
2012-04-25 18:14 ` Greg Kroah-Hartman
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=4F98A90C.9020705@kernel.org \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dan.magenheimer@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 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).