From: Michal Hocko <mhocko@kernel.org>
To: Jia He <hejianet@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Mel Gorman <mgorman@techsingularity.net>,
Vlastimil Babka <vbabka@suse.cz>,
Minchan Kim <minchan@kernel.org>, Rik van Riel <riel@redhat.com>
Subject: Re: [RFC PATCH] mm/vmscan: fix high cpu usage of kswapd if there
Date: Wed, 22 Feb 2017 12:41:05 +0100 [thread overview]
Message-ID: <20170222114105.GI5753@dhcp22.suse.cz> (raw)
In-Reply-To: <1487754288-5149-1-git-send-email-hejianet@gmail.com>
On Wed 22-02-17 17:04:48, Jia He wrote:
> When I try to dynamically allocate the hugepages more than system total
> free memory:
> e.g. echo 4000 >/proc/sys/vm/nr_hugepages
I assume that the command has terminated with less huge pages allocated
than requested but
> Node 3, zone DMA
[...]
> pages free 2951
> min 2821
> low 3526
> high 4231
it left the zone below high watermark with
> node_scanned 0
> spanned 245760
> present 245760
> managed 245388
> nr_free_pages 2951
> nr_zone_inactive_anon 0
> nr_zone_active_anon 0
> nr_zone_inactive_file 0
> nr_zone_active_file 0
no pages reclaimable, so kswapd will not go to sleep. It would be quite
easy and comfortable to call it a misconfiguration but it seems that
it might be quite easy to hit with NUMA machines which have large
differences in the node sizes. I guess it makes sense to back off
the kswapd rather than burning CPU without any way to make forward
progress.
[...]
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index 532a2a7..a05e3ab 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -3139,7 +3139,8 @@ static bool prepare_kswapd_sleep(pg_data_t *pgdat, int order, int classzone_idx)
> if (!managed_zone(zone))
> continue;
>
> - if (!zone_balanced(zone, order, classzone_idx))
> + if (!zone_balanced(zone, order, classzone_idx)
> + && zone_reclaimable_pages(zone))
> return false;
OK, this makes some sense, although zone_reclaimable_pages doesn't count
SLAB reclaimable pages. So we might go to sleep with a reclaimable slab
still around. This is not really easy to address because the reclaimable
slab doesn't really imply that those pages will be reclaimed...
> }
>
> @@ -3502,6 +3503,7 @@ void wakeup_kswapd(struct zone *zone, int order, enum zone_type classzone_idx)
> {
> pg_data_t *pgdat;
> int z;
> + int node_has_relaimable_pages = 0;
>
> if (!managed_zone(zone))
> return;
> @@ -3522,8 +3524,15 @@ void wakeup_kswapd(struct zone *zone, int order, enum zone_type classzone_idx)
>
> if (zone_balanced(zone, order, classzone_idx))
> return;
> +
> + if (!zone_reclaimable_pages(zone))
> + node_has_relaimable_pages = 1;
What, this doesn't make any sense? Did you mean if (zone_reclaimable_pages)?
> }
>
> + /* Dont wake kswapd if no reclaimable pages */
> + if (!node_has_relaimable_pages)
> + return;
> +
> trace_mm_vmscan_wakeup_kswapd(pgdat->node_id, zone_idx(zone), order);
> wake_up_interruptible(&pgdat->kswapd_wait);
> }
> --
> 1.8.5.6
>
> --
> 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>
--
Michal Hocko
SUSE Labs
--
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:[~2017-02-22 11:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 9:04 Jia He
2017-02-22 11:41 ` Michal Hocko [this message]
2017-02-22 14:31 ` hejianet
2017-02-22 15:48 ` Michal Hocko
2017-02-23 2:25 ` hejianet
2017-02-22 20:16 ` Johannes Weiner
2017-02-22 20:24 ` Johannes Weiner
2017-02-23 7:29 ` Michal Hocko
2017-02-23 2:24 ` hejianet
2017-02-23 2:46 ` hejianet
2017-02-23 7:21 ` Michal Hocko
2017-02-23 10:19 ` Michal Hocko
2017-02-23 11:16 ` Michal Hocko
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=20170222114105.GI5753@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hejianet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=minchan@kernel.org \
--cc=riel@redhat.com \
--cc=vbabka@suse.cz \
/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