linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hao Ge <gehao618@163.com>
To: Hao Ge <gehao@kylinos.cn>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs/inode: Make too_many_isolated return bool
Date: Mon, 5 Feb 2024 12:23:32 +0800	[thread overview]
Message-ID: <02CFAD55-0733-4765-9160-153409AE050F@163.com> (raw)
In-Reply-To: <20240205022825.99061-1-gehao@kylinos.cn>

Sorry, please ignore this patch due to an incorrect title. I will resend the correct one

> On Feb 5, 2024, at 10:28, Hao Ge <gehao@kylinos.cn> wrote:
> 
> too_many_isolated should return bool which with the same name and
> similar functions in mm/compaction.c already returned bool
> 
> Signed-off-by: Hao Ge <gehao@kylinos.cn>
> ---
> mm/vmscan.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index 4f9c854ce6cc..143e4b8e8821 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -1744,17 +1744,17 @@ bool folio_isolate_lru(struct folio *folio)
>  * the LRU list will go small and be scanned faster than necessary, leading to
>  * unnecessary swapping, thrashing and OOM.
>  */
> -static int too_many_isolated(struct pglist_data *pgdat, int file,
> +static bool too_many_isolated(struct pglist_data *pgdat, int file,
>        struct scan_control *sc)
> {
>    unsigned long inactive, isolated;
>    bool too_many;
> 
>    if (current_is_kswapd())
> -        return 0;
> +        return false;
> 
>    if (!writeback_throttling_sane(sc))
> -        return 0;
> +        return false;
> 
>    if (file) {
>        inactive = node_page_state(pgdat, NR_INACTIVE_FILE);
> --
> 2.25.1



      reply	other threads:[~2024-02-05  4:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05  2:28 Hao Ge
2024-02-05  4:23 ` Hao Ge [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=02CFAD55-0733-4765-9160-153409AE050F@163.com \
    --to=gehao618@163.com \
    --cc=akpm@linux-foundation.org \
    --cc=gehao@kylinos.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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