linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: SeongJae Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, <linux-mm@kvack.org>,
	<linux-kernel@vger.kernel.org>, <damon@lists.linux.dev>
Subject: Re: [PATCH -next] mm/damon/paddr: minor refactor of damon_pa_pageout()
Date: Fri, 3 Mar 2023 09:42:04 +0800	[thread overview]
Message-ID: <927fbb66-ee80-2ec4-60d1-1cda23b3cb19@huawei.com> (raw)
In-Reply-To: <20230302164706.85999-1-sj@kernel.org>



On 2023/3/3 0:47, SeongJae Park wrote:
> Hi Kefeng,
> 
> On Thu, 2 Mar 2023 22:49:26 +0800 Kefeng Wang <wangkefeng.wang@huawei.com> wrote:
> 
>> Omit two lines by converting if(!folio_isolate_lru()) to
>> if(folio_isolate_lru()).
>>
>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>> ---
>>   mm/damon/paddr.c | 12 +++++-------
>>   1 file changed, 5 insertions(+), 7 deletions(-)
>>
>> diff --git a/mm/damon/paddr.c b/mm/damon/paddr.c
>> index 6c655d9b5639..a557f3c9300f 100644
>> --- a/mm/damon/paddr.c
>> +++ b/mm/damon/paddr.c
>> @@ -246,14 +246,12 @@ static unsigned long damon_pa_pageout(struct damon_region *r, struct damos *s)
>>   
>>   		folio_clear_referenced(folio);
>>   		folio_test_clear_young(folio);
>> -		if (!folio_isolate_lru(folio)) {
>> -			folio_put(folio);
>> -			continue;
>> +		if (folio_isolate_lru(folio)) {
>> +			if (folio_test_unevictable(folio))
>> +				folio_putback_lru(folio);
>> +			else
>> +				list_add(&folio->lru, &folio_list);
>>   		}
>> -		if (folio_test_unevictable(folio))
>> -			folio_putback_lru(folio);
>> -		else
>> -			list_add(&folio->lru, &folio_list);
>>   		folio_put(folio);
>>   	}
> 
> This looks ok to me, thank you for your effort!  Nevertheless, I don't like
> increasing depth as much as number of lines.  The
> more-than-3-levels-of-indentation[1] warning is not always right, but this 4
> levels of indentation is not making me so exciting.
> 
> What do you think about adding put_continue label and using it, not only here,
> but also above part?  For example:
> 
>      --- a/mm/damon/paddr.c
>      +++ b/mm/damon/paddr.c
>      @@ -239,21 +239,18 @@ static unsigned long damon_pa_pageout(struct damon_region *r, struct damos *s)
>                      if (!folio)
>                              continue;
>      
>      -               if (damos_pa_filter_out(s, folio)) {
>      -                       folio_put(folio);
>      -                       continue;
>      -               }
>      +               if (damos_pa_filter_out(s, folio))
>      +                       goto put_continue;
>      
>                      folio_clear_referenced(folio);
>                      folio_test_clear_young(folio);
>      -               if (!folio_isolate_lru(folio)) {
>      -                       folio_put(folio);
>      -                       continue;
>      -               }
>      +               if (!folio_isolate_lru(folio))
>      +                       goto put_continue;
>                      if (folio_test_unevictable(folio))
>                              folio_putback_lru(folio);
>                      else
>                              list_add(&folio->lru, &folio_list);
>      +put_continue:
>                      folio_put(folio);
>              }
>              applied = reclaim_pages(&folio_list);
> 
> It omits three lines.

It looks good, will update, thanks

> 
>      $ git diff --stat
>       mm/damon/paddr.c | 13 +++++--------
>       1 file changed, 5 insertions(+), 8 deletions(-)
> 
> [1] https://docs.kernel.org/process/coding-style.html#indentation
> 
> 
> Thanks,
> SJ
> 
>>   	applied = reclaim_pages(&folio_list);
>> -- 
>> 2.35.3
>>
>>


      reply	other threads:[~2023-03-03  1:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 14:49 Kefeng Wang
2023-03-02 16:47 ` SeongJae Park
2023-03-03  1:42   ` Kefeng Wang [this message]

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=927fbb66-ee80-2ec4-60d1-1cda23b3cb19@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=damon@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sj@kernel.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