linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Zhaoyang Huang <huangzhaoyang@gmail.com>,
	"zhaoyang.huang" <zhaoyang.huang@unisoc.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	"open list:MEMORY MANAGEMENT" <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>, Ke Wang <ke.wang@unisoc.com>
Subject: Re: [PATCH] mm: skip reserved page for kmem leak scanning
Date: Mon, 29 Aug 2022 14:18:58 +0200	[thread overview]
Message-ID: <12759ac7-4a6c-89fa-5fd0-914728f6415e@redhat.com> (raw)
In-Reply-To: <CAGWkznH=Gwr_TDF3=fv+_ZH5P4QN6JXEAtH4DAzNus20pHxyeg@mail.gmail.com>

On 26.08.22 05:23, Zhaoyang Huang wrote:
> On Fri, Aug 26, 2022 at 11:13 AM zhaoyang.huang
> <zhaoyang.huang@unisoc.com> wrote:
>>
>> From: Zhaoyang Huang <zhaoyang.huang@unisoc.com>
>>
>> It is no need to scan reserved page, skip it.
>>
>> Signed-off-by: Zhaoyang Huang <zhaoyang.huang@unisoc.com>
>> ---
>>  mm/kmemleak.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/mm/kmemleak.c b/mm/kmemleak.c
>> index a182f5d..c546250 100644
>> --- a/mm/kmemleak.c
>> +++ b/mm/kmemleak.c
>> @@ -1471,7 +1471,7 @@ static void kmemleak_scan(void)
>>                         if (page_zone(page) != zone)
>>                                 continue;
>>                         /* only scan if page is in use */
>> -                       if (page_count(page) == 0)
>> +                       if (page_count(page) == 0 || PageReserved(page))
> Sorry for previous stupid code by my faint, correct it here

Did you even test the initial patch?

I wonder why we should consider this change

(a) I doubt it's a performance issue. If it is, please provide numbers
    before/after.
(b) We'll stop scanning early allocations. As the memmap is usually
    allocated early during boot ... we'll stop scanning essentially the
    whole mmap and that whole loop would be dead code? What am i
    missing?

-- 
Thanks,

David / dhildenb



  reply	other threads:[~2022-08-29 12:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26  3:12 zhaoyang.huang
2022-08-26  3:23 ` Zhaoyang Huang
2022-08-29 12:18   ` David Hildenbrand [this message]
2022-08-30  2:41     ` Zhaoyang Huang
2022-08-30  8:03       ` David Hildenbrand
2022-08-30  8:52         ` Zhaoyang Huang

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=12759ac7-4a6c-89fa-5fd0-914728f6415e@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=huangzhaoyang@gmail.com \
    --cc=ke.wang@unisoc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=zhaoyang.huang@unisoc.com \
    /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