archive mirror
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <>
To: Mike Rapoport <>
	Andrew Morton <>,
	Kefeng Wang <>,
	Mike Rapoport <>,,
Subject: Re: [PATCH 3/3] arm: extend pfn_valid to take into accound freed memory map alignment
Date: Tue, 18 May 2021 10:44:27 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, May 18, 2021 at 12:06:13PM +0300, Mike Rapoport wrote:
> From: Mike Rapoport <>
> When unused memory map is freed the preserved part of the memory map is
> extended to match pageblock boundaries because lots of core mm
> functionality relies on homogeneity of the memory map within pageblock
> boundaries.
> Since pfn_valid() is used to check whether there is a valid memory map
> entry for a PFN, make it return true also for PFNs that have memory map
> entries even if there is no actual memory populated there.

I thought pfn_valid() was a particularly hot path... do we really want
to be doing multiple lookups here? Is there no better solution?

RMK's Patch system:
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

linux-arm-kernel mailing list

  reply	other threads:[~2021-05-18  9:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18  9:06 [PATCH 0/3] memblock, arm: fixes for freeing of the memory map Mike Rapoport
2021-05-18  9:06 ` [PATCH 1/3] memblock: free_unused_memmap: use pageblock units instead of MAX_ORDER Mike Rapoport
2021-05-18  9:06 ` [PATCH 2/3] memblock: align freed memory map on pageblock boundaries with SPARSEMEM Mike Rapoport
2021-05-18  9:06 ` [PATCH 3/3] arm: extend pfn_valid to take into accound freed memory map alignment Mike Rapoport
2021-05-18  9:44   ` Russell King (Oracle) [this message]
2021-05-18 10:53     ` Mike Rapoport
2021-05-18 12:49   ` Kefeng Wang
2021-05-18 15:52     ` Mike Rapoport
2021-05-19  1:50       ` Kefeng Wang
2021-05-19 13:25         ` Mike Rapoport

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \

* 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).