[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200403134439.li6i635dnur5jdha@ca-dmjordan1.us.oracle.com>
Date: Fri, 3 Apr 2020 09:44:39 -0400
From: Daniel Jordan <daniel.m.jordan@...cle.com>
To: Pavel Tatashin <pasha.tatashin@...een.com>
Cc: linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
mhocko@...e.com, linux-mm@...ck.org, dan.j.williams@...el.com,
shile.zhang@...ux.alibaba.com, daniel.m.jordan@...cle.com,
ktkhai@...tuozzo.com, david@...hat.com, jmorris@...ei.org,
sashal@...nel.org, vbabka@...e.cz
Subject: Re: [PATCH v3 3/3] mm: call cond_resched() from
deferred_init_memmap()
On Fri, Apr 03, 2020 at 09:35:49AM -0400, Pavel Tatashin wrote:
> Now that deferred pages are initialized with interrupts enabled we can
> replace touch_nmi_watchdog() with cond_resched(), as it was before
> 3a2d7fa8a3d5.
...
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 4a60f2427eb0..445f74358997 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -1816,7 +1816,7 @@ static int __init deferred_init_memmap(void *data)
> */
> while (spfn < epfn) {
> nr_pages += deferred_init_maxorder(&i, zone, &spfn, &epfn);
> - touch_nmi_watchdog();
> + sched_clock();
I think you meant cond_resched()?
With that,
Reviewed-by: Daniel Jordan <daniel.m.jordan@...cle.com>
Powered by blists - more mailing lists