From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Kassey Li <quic_yingangl@quicinc.com>,
Matthew Wilcox <willy@infradead.org>
Cc: akpm@linux-foundation.org, minchan@kernel.org,
iamjoonsoo.kim@lge.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, quic_guptap@quicinc.com
Subject: Re: [PATCH] mm/page_owner.c: allow page_owner with given start_pfn/count
Date: Tue, 26 Jul 2022 16:03:47 +0200 [thread overview]
Message-ID: <ce6f3bcf-fe77-d042-4517-dd09d090b70b@kernel.org> (raw)
In-Reply-To: <e518246c-4ffa-14af-e568-798572f75bee@quicinc.com>
On 7/25/22 10:39, Kassey Li wrote:
> 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.
You could try employing lseek() to specify the start pfn, and as for end
pfn, the process can just stop reading and close when it has seen enough?
> 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?
>
next prev parent reply other threads:[~2022-07-26 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 15:08 [PATCH] mm/page_owner.c: allow page_owner with given start_pfn/count Kassey Li
2022-07-22 15:38 ` Matthew Wilcox
2022-07-25 8:39 ` Kassey Li
2022-07-26 14:03 ` Vlastimil Babka (SUSE) [this message]
2022-07-27 7:44 ` Kassey Li
2022-07-27 10:59 ` Vlastimil Babka (SUSE)
2022-07-27 12:58 ` Kassey Li
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=ce6f3bcf-fe77-d042-4517-dd09d090b70b@kernel.org \
--to=vbabka@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=quic_guptap@quicinc.com \
--cc=quic_yingangl@quicinc.com \
--cc=willy@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).