mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yang Shi <yang@os.amperecomputing.com>
To: Catalin Marinas <cmarinas@kernel.org>,
	ryan.roberts@arm.com, cl@gentwo.org, will@kernel.org
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [v2 PATCH] arm64: mm: show direct mapping use in /proc/meminfo
Date: Wed, 19 Nov 2025 11:37:13 -0800	[thread overview]
Message-ID: <76803fd4-7a7c-4018-b2cc-8e36cba60729@os.amperecomputing.com> (raw)
In-Reply-To: <176357957114.2095636.13353317001365823131.b4-ty@arm.com>



On 11/19/25 11:12 AM, Catalin Marinas wrote:
> From: Catalin Marinas <catalin.marinas@arm.com>
>
> On Thu, 23 Oct 2025 14:52:10 -0700, Yang Shi wrote:
>> Since commit a166563e7ec3 ("arm64: mm: support large block mapping when
>> rodata=full"), the direct mapping may be split on some machines instead
>> keeping static since boot. It makes more sense to show the direct mapping
>> use in /proc/meminfo than before.
>> This patch will make /proc/meminfo show the direct mapping use like the
>> below (4K base page size):
>> DirectMap4K:	   94792 kB
>> DirectMap64K:	  134208 kB
>> DirectMap2M:	 1173504 kB
>> DirectMap32M:	 5636096 kB
>> DirectMap1G:	529530880 kB
>>
>> [...]
> It matches Documentation/filesystems/proc.rst, so I'm fine to align
> arm64 with it.

Yes, it does.

>
> Applied to arm64 (for-next/misc), thanks!
>
> [1/1] arm64: mm: show direct mapping use in /proc/meminfo
>        https://git.kernel.org/arm64/c/1102778cb023

Thanks for taking the patch. However, Ryan noticed some over-accounting 
problems and had some suggestions to code cleanup as well. I'm going to 
submit v3 to the mailing list soon.

Yang
>


  reply	other threads:[~2025-11-19 19:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-23 21:52 Yang Shi
2025-11-10 23:06 ` Yang Shi
2025-11-12 10:16 ` Ryan Roberts
2025-11-12 17:11   ` Christoph Lameter (Ampere)
2025-11-13 11:29     ` Ryan Roberts
2025-11-12 22:24   ` Yang Shi
2025-11-13 11:28     ` Ryan Roberts
2025-11-13 18:14       ` Yang Shi
2025-11-20  8:38         ` Ryan Roberts
2025-11-20 17:33           ` Yang Shi
2025-11-19 19:12 ` Catalin Marinas
2025-11-19 19:37   ` Yang Shi [this message]
2025-11-19 21:10     ` Catalin Marinas
2025-11-19 22:26       ` Yang Shi

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=76803fd4-7a7c-4018-b2cc-8e36cba60729@os.amperecomputing.com \
    --to=yang@os.amperecomputing.com \
    --cc=catalin.marinas@arm.com \
    --cc=cl@gentwo.org \
    --cc=cmarinas@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ryan.roberts@arm.com \
    --cc=will@kernel.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

all inboxes | Powered by JetHome®