public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: Wei Yang <richard.weiyang@gmail.com>
To: Jaewon Kim <jaewon31.kim@samsung.com>
Cc: "richard.weiyang@gmail.com" <richard.weiyang@gmail.com>,
	Mike Rapoport <rppt@kernel.org>,
	"vbabka@suse.cz" <vbabka@suse.cz>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"jaewon31.kim@gmail.com" <jaewon31.kim@gmail.com>,
	"tkjos@google.com" <tkjos@google.com>
Subject: Re: [RESEND PATCH 00/10] memblock: introduce memsize showing reserved memory
Date: Thu, 23 May 2024 08:55:54 +0000	[thread overview]
Message-ID: <20240523085554.netvftdebmg5ie4a@master> (raw)
In-Reply-To: <20240522084738epcms1p80845ffecee4fbab97b34fdf2ce1595a7@epcms1p8>

On Wed, May 22, 2024 at 05:47:38PM +0900, Jaewon Kim wrote:
[...]
>
>Hi
>
>> Maybe you can show the log difference, so that we can see how it helps you.
>
>For your new email, could you elaborate the difference you meant? 
>Do you mean difference between existing debugfs membock interfaces and the one I introdued here?
>

You mentioned the difference between kernel version helps you locate the
problem. That is the difference of your new debugfs.


-- 
Wei Yang
Help you, Help me


  reply	other threads:[~2024-05-23  8:56 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20240521024009epcas1p10ed9f9b929203183a29f79508e79bb76@epcas1p1.samsung.com>
2024-05-21  2:39 ` [RESEND PATCH 00/10] memblock: introduce memsize showing reserved memory Jaewon Kim
2024-05-21  2:39   ` [RESEND PATCH 01/10] " Jaewon Kim
2024-05-21  2:39   ` [RESEND PATCH 02/10] memblock: detect hidden memory hole size Jaewon Kim
2024-05-21  2:39   ` [RESEND PATCH 03/10] memblock: handle overlapped reserved memory region Jaewon Kim
2024-05-21  2:39   ` [RESEND PATCH 04/10] memblock: take a region intersecting an unknown region Jaewon Kim
2024-05-21  2:39   ` [RESEND PATCH 05/10] memblock: track memblock changed at early param Jaewon Kim
2024-05-21  2:39   ` [RESEND PATCH 06/10] memblock: recognize late freed size by checking PageReserved Jaewon Kim
2024-05-21  2:39   ` [RESEND PATCH 07/10] memblock: track kernel size on memsize Jaewon Kim
2024-05-22 19:03     ` kernel test robot
2024-05-21  2:39   ` [RESEND PATCH 08/10] memblock: print memsize summary information Jaewon Kim
2024-05-21  2:39   ` [RESEND PATCH 09/10] memblock: print kernel internal size Jaewon Kim
2024-05-22 18:52     ` kernel test robot
2024-05-21  2:39   ` [RESEND PATCH 10/10] memblock: support memsize reusable to consider as reusable Jaewon Kim
2024-05-22 22:40     ` kernel test robot
2024-05-23 10:55       ` Jaewon Kim
2024-05-21  2:53   ` [RESEND PATCH 00/10] memblock: introduce memsize showing reserved memory Jaewon Kim
2024-05-21  7:31     ` Mike Rapoport
2024-05-21 10:17       ` Jaewon Kim
2024-05-22  8:16         ` (2) " Wei Yang
2024-05-22  8:47           ` Jaewon Kim
2024-05-23  8:55             ` Wei Yang [this message]
2024-05-23  9:23               ` 김재원
2024-05-23 14:34         ` (2) " Mike Rapoport
2024-05-24  9:07           ` Jaewon Kim
2024-05-26 13:55             ` Mike Rapoport
2024-05-27  1:30               ` Jaewon Kim
2024-05-27  1:35               ` Jaewon Kim
2024-05-27 16:22                 ` Mike Rapoport
     [not found]             ` <CGME20240521024009epcas1p10ed9f9b929203183a29f79508e79bb76@epcms1p7>
     [not found]               ` <20240529095119epcms1p73f0e9ff756bcb2ee6a14db459128a644@epcms1p7>
2024-05-29 11:35                 ` Wei Yang
2024-05-29 13:10                   ` Jaewon Kim
2024-05-30  0:03                     ` Wei Yang
2024-05-30 10:49                       ` Jaewon Kim
2024-05-31  1:05                         ` (2) " Wei Yang
2024-05-31  8:21                           ` Jaewon Kim
2024-06-01  1:40                             ` Wei Yang
2024-06-03  9:33                               ` Jaewon Kim
2024-05-24 17:33           ` Pintu Agarwal
2024-05-22  8:20     ` Wei Yang

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=20240523085554.netvftdebmg5ie4a@master \
    --to=richard.weiyang@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=jaewon31.kim@gmail.com \
    --cc=jaewon31.kim@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rppt@kernel.org \
    --cc=tkjos@google.com \
    --cc=vbabka@suse.cz \
    /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