[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e518246c-4ffa-14af-e568-798572f75bee@quicinc.com>
Date: Mon, 25 Jul 2022 16:39:03 +0800
From: Kassey Li <quic_yingangl@...cinc.com>
To: Matthew Wilcox <willy@...radead.org>
CC: <akpm@...ux-foundation.org>, <minchan@...nel.org>,
<iamjoonsoo.kim@....com>, <linux-kernel@...r.kernel.org>,
<linux-mm@...ck.org>, <quic_guptap@...cinc.com>
Subject: Re: [PATCH] mm/page_owner.c: allow page_owner with given
start_pfn/count
hi, Matthew:
sorry for the delay, I just started to learn how to upstream patch, and
setup my Thunderbird with plain text only.
you are right, two users will cause problem here.
the uses case is dump CMA area to understand the page usage in a given
cma pool. 2nd, dump whole memory page owner is very time cost, mostly
our android device has 8G memory now.
I will research and check again, if you have more idea on this , please
kindly to share.
BR
Kassey
On 7/22/2022 11:38 PM, Matthew Wilcox wrote:
> On Fri, Jul 22, 2022 at 11:08:10PM +0800, Kassey Li wrote:
>> by default, page_owner iterates all page from min_low_pfn to
>> max_pfn, this cost too much time if we want an alternative pfn range.
>>
>> with this patch it allows user to set pfn range to dump the page_onwer.
>
> This is a really bad UI. If two users try to do different ranges at the
> same time, it'll go wrong. What use cases are you actually trying to
> solve?
Powered by blists - more mailing lists