linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ganesh Mahendran <opensource.ganesh@gmail.com>
To: Dan Streetman <ddstreet@ieee.org>
Cc: Minchan Kim <minchan@kernel.org>, Nitin Gupta <ngupta@vflare.org>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	Linux-MM <linux-mm@kvack.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/zsmalloc: avoid duplicate assignment of prev_class
Date: Fri, 21 Nov 2014 13:22:21 +0800	[thread overview]
Message-ID: <CADAEsF8+BbQO0-cbL0KRxbaH_nisG=_Gukr=_=nkYaCwR+sqQw@mail.gmail.com> (raw)
In-Reply-To: <CALZtONAdpiP+DZfJBYG9EYN+8pTToMnAaUGemZ-r7x8YcQXbCQ@mail.gmail.com>

Hello

2014-11-21 11:22 GMT+08:00 Dan Streetman <ddstreet@ieee.org>:
> On Thu, Nov 20, 2014 at 8:08 AM, Mahendran Ganesh
> <opensource.ganesh@gmail.com> wrote:
>> In zs_create_pool(), prev_class is assigned (ZS_SIZE_CLASSES - 1)
>> times. And the prev_class only references to the previous alloc
>> size_class. So we do not need unnecessary assignement.
>>
>> This patch modifies *prev_class* to *prev_alloc_class*. And the
>> *prev_alloc_class* will only be assigned when a new size_class
>> structure is allocated.
>>
>> Signed-off-by: Mahendran Ganesh <opensource.ganesh@gmail.com>
>> ---
>>  mm/zsmalloc.c |    9 +++++----
>>  1 file changed, 5 insertions(+), 4 deletions(-)
>>
>> diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c
>> index b3b57ef..ac2b396 100644
>> --- a/mm/zsmalloc.c
>> +++ b/mm/zsmalloc.c
>> @@ -970,7 +970,7 @@ struct zs_pool *zs_create_pool(gfp_t flags)
>>                 int size;
>>                 int pages_per_zspage;
>>                 struct size_class *class;
>> -               struct size_class *prev_class;
>> +               struct size_class *uninitialized_var(prev_alloc_class);
>
> +               struct size_class *prev_class = NULL;
>
> Use the fact it's unset below, so set it to NULL here

Yes, You are right. I will change it in next resend.
Thanks for your review.

>
>>
>>                 size = ZS_MIN_ALLOC_SIZE + i * ZS_SIZE_CLASS_DELTA;
>>                 if (size > ZS_MAX_ALLOC_SIZE)
>> @@ -987,9 +987,8 @@ struct zs_pool *zs_create_pool(gfp_t flags)
>>                  * previous size_class if possible.
>>                  */
>>                 if (i < ZS_SIZE_CLASSES - 1) {
>> -                       prev_class = pool->size_class[i + 1];
>> -                       if (can_merge(prev_class, size, pages_per_zspage)) {
>> -                               pool->size_class[i] = prev_class;
>> +                       if (can_merge(prev_alloc_class, size, pages_per_zspage)) {
>> +                               pool->size_class[i] = prev_alloc_class;
>
> simplify more, we can check if this is the first iteration by looking
> at prev_class, e.g.:
>
>                 if (prev_class) {
>                        if (can_merge(prev_class, size, pages_per_zspage)) {
>                                pool->size_class[i] = prev_class;
>
>
>>                                 continue;
>>                         }
>>                 }
>> @@ -1003,6 +1002,8 @@ struct zs_pool *zs_create_pool(gfp_t flags)
>>                 class->pages_per_zspage = pages_per_zspage;
>>                 spin_lock_init(&class->lock);
>>                 pool->size_class[i] = class;
>> +
>> +               prev_alloc_class = class;
>>         }
>>
>>         pool->flags = flags;
>> --
>> 1.7.9.5
>>
>> --
>> 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>

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

  reply	other threads:[~2014-11-21  5:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 13:08 Mahendran Ganesh
2014-11-21  3:22 ` Dan Streetman
2014-11-21  5:22   ` Ganesh Mahendran [this message]
2014-11-21  3:43 ` Minchan Kim
2014-11-21  5:25   ` Ganesh Mahendran

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='CADAEsF8+BbQO0-cbL0KRxbaH_nisG=_Gukr=_=nkYaCwR+sqQw@mail.gmail.com' \
    --to=opensource.ganesh@gmail.com \
    --cc=ddstreet@ieee.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=ngupta@vflare.org \
    /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