From: Minchan Kim <minchan@kernel.org>
To: Ganesh Mahendran <opensource.ganesh@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, ngupta@vflare.org,
sergey.senozhatsky.work@gmail.com, rostedt@goodmis.org,
mingo@redhat.com
Subject: Re: [PATCH 5/8] mm/zsmalloc: avoid calculate max objects of zspage twice
Date: Mon, 4 Jul 2016 09:03:18 +0900 [thread overview]
Message-ID: <20160704000317.GD19044@bbox> (raw)
In-Reply-To: <1467355266-9735-5-git-send-email-opensource.ganesh@gmail.com>
On Fri, Jul 01, 2016 at 02:41:03PM +0800, Ganesh Mahendran wrote:
> Currently, if a class can not be merged, the max objects of zspage
> in that class may be calculated twice.
>
> This patch calculate max objects of zspage at the begin, and pass
> the value to can_merge() to decide whether the class can be merged.
>
> Signed-off-by: Ganesh Mahendran <opensource.ganesh@gmail.com>
> ---
> mm/zsmalloc.c | 21 ++++++++++-----------
> 1 file changed, 10 insertions(+), 11 deletions(-)
>
> diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c
> index 50283b1..2690914 100644
> --- a/mm/zsmalloc.c
> +++ b/mm/zsmalloc.c
> @@ -1362,16 +1362,14 @@ static void init_zs_size_classes(void)
> zs_size_classes = nr;
> }
>
> -static bool can_merge(struct size_class *prev, int size, int pages_per_zspage)
> +static bool can_merge(struct size_class *prev, int pages_per_zspage,
> + int objs_per_zspage)
> {
> - if (prev->pages_per_zspage != pages_per_zspage)
> - return false;
> -
> - if (prev->objs_per_zspage
> - != get_maxobj_per_zspage(size, pages_per_zspage))
> - return false;
> + if (prev->pages_per_zspage == pages_per_zspage &&
> + prev->objs_per_zspage == objs_per_zspage)
> + return true;
>
> - return true;
> + return false;
> }
>
> static bool zspage_full(struct size_class *class, struct zspage *zspage)
> @@ -2460,6 +2458,7 @@ struct zs_pool *zs_create_pool(const char *name)
> for (i = zs_size_classes - 1; i >= 0; i--) {
> int size;
> int pages_per_zspage;
> + int objs_per_zspage;
> struct size_class *class;
> int fullness = 0;
>
> @@ -2467,6 +2466,7 @@ struct zs_pool *zs_create_pool(const char *name)
> if (size > ZS_MAX_ALLOC_SIZE)
> size = ZS_MAX_ALLOC_SIZE;
> pages_per_zspage = get_pages_per_zspage(size);
> + objs_per_zspage = get_maxobj_per_zspage(size, pages_per_zspage);
So, user of get_maxobj_per_zspage is only here? If so, let's remove
get_maxobj_per_zspage to prevent misuse in future. Instead, use open code
here.
>
> /*
> * size_class is used for normal zsmalloc operation such
> @@ -2478,7 +2478,7 @@ struct zs_pool *zs_create_pool(const char *name)
> * previous size_class if possible.
> */
> if (prev_class) {
> - if (can_merge(prev_class, size, pages_per_zspage)) {
> + if (can_merge(prev_class, pages_per_zspage, objs_per_zspage)) {
> pool->size_class[i] = prev_class;
> continue;
> }
> @@ -2491,8 +2491,7 @@ struct zs_pool *zs_create_pool(const char *name)
> class->size = size;
> class->index = i;
> class->pages_per_zspage = pages_per_zspage;
> - class->objs_per_zspage = get_maxobj_per_zspage(class->size,
> - class->pages_per_zspage);
> + class->objs_per_zspage = objs_per_zspage;
> spin_lock_init(&class->lock);
> pool->size_class[i] = class;
> for (fullness = ZS_EMPTY; fullness < NR_ZS_FULLNESS;
> --
> 1.9.1
>
--
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>
next prev parent reply other threads:[~2016-07-04 0:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 6:40 [PATCH 1/8] mm/zsmalloc: modify zs compact trace interface Ganesh Mahendran
2016-07-01 6:41 ` [PATCH 2/8] mm/zsmalloc: add per class compact trace event Ganesh Mahendran
2016-07-03 23:49 ` Minchan Kim
2016-07-04 3:12 ` Ganesh Mahendran
2016-07-01 6:41 ` [PATCH 3/8] mm/zsmalloc: take obj index back from find_alloced_obj Ganesh Mahendran
2016-07-03 23:57 ` Minchan Kim
2016-07-04 3:23 ` Ganesh Mahendran
2016-07-01 6:41 ` [PATCH 4/8] mm/zsmalloc: use class->objs_per_zspage to get num of max objects Ganesh Mahendran
2016-07-03 23:58 ` Minchan Kim
2016-07-01 6:41 ` [PATCH 5/8] mm/zsmalloc: avoid calculate max objects of zspage twice Ganesh Mahendran
2016-07-04 0:03 ` Minchan Kim [this message]
2016-07-04 3:26 ` Ganesh Mahendran
2016-07-01 6:41 ` [PATCH 6/8] mm/zsmalloc: keep comments consistent with code Ganesh Mahendran
2016-07-04 0:05 ` Minchan Kim
2016-07-04 3:32 ` Ganesh Mahendran
2016-07-01 6:41 ` [PATCH 7/8] mm/zsmalloc: add __init,__exit attribute Ganesh Mahendran
2016-07-04 0:09 ` Minchan Kim
2016-07-01 6:41 ` [PATCH 8/8] mm/zsmalloc: use helper to clear page->flags bit Ganesh Mahendran
2016-07-04 0:11 ` Minchan Kim
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=20160704000317.GD19044@bbox \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=ngupta@vflare.org \
--cc=opensource.ganesh@gmail.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.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).