[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171117182722.vhgzd5rj3qgv7a6f@armageddon.cambridge.arm.com>
Date: Fri, 17 Nov 2017 18:27:22 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: Yisheng Xie <xieyisheng1@...wei.com>
Cc: akpm@...ux-foundation.org, mhocko@...nel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kmemcheck: add scheduling point to kmemleak_scan
Please fix the subject as the tool is called "kmemleak" rather than
"kmemcheck".
On Fri, Nov 17, 2017 at 03:03:56PM +0800, Yisheng Xie wrote:
> diff --git a/mm/kmemleak.c b/mm/kmemleak.c
> index e4738d5..e9f2e86 100644
> --- a/mm/kmemleak.c
> +++ b/mm/kmemleak.c
> @@ -1523,6 +1523,8 @@ static void kmemleak_scan(void)
> if (page_count(page) == 0)
> continue;
> scan_block(page, page + 1, NULL);
> + if (!(pfn % 1024))
> + cond_resched();
For consistency with the other places where we call cond_resched() in
kmemleak, I would use MAX_SCAN_SIZE. Something like
if (!(pfn % (MAX_SCAN_SIZE / sizeof(page))))
cont_resched();
Thanks.
--
Catalin
Powered by blists - more mailing lists