From: Brendan Jackman <jackmanb@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Mel Gorman <mgorman@techsingularity.net>,
Michal Hocko <mhocko@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Brendan Jackman <jackmanb@google.com>,
Yosry Ahmed <yosry.ahmed@linux.dev>
Subject: [PATCH v4 0/2] mm/page_alloc: Some clarifications for migratetype fallback
Date: Fri, 28 Feb 2025 09:52:16 +0000 [thread overview]
Message-ID: <20250228-clarify-steal-v4-0-cb2ef1a4e610@google.com> (raw)
A couple of patches to try and make the code easier to follow.
This is based on an old mm-unstable as v3 is already merged there. Base
commit info is attached below.
Signed-off-by: Brendan Jackman <jackmanb@google.com>
---
Changes in v4:
- Some more precision about "try to claim" vs "claim"
- More improvements to the commentary text.
- Link to v3: https://lore.kernel.org/r/20250225-clarify-steal-v3-0-f2550ead0139@google.com
Changes in v3:
- Rebased onto mm-unstable to get on top of Johannes' cleanups:
https://lore.kernel.org/linux-mm/20250225001023.1494422-1-hannes@cmpxchg.org/
- Fixed missing renames
- Link to v2: https://lore.kernel.org/r/20250224-clarify-steal-v2-0-be24da656764@google.com
Changes in v2:
- Tweaked some naming
- Added clarifications of should_claim_block()
- Link to v1: https://lore.kernel.org/r/20250214-clarify-steal-v1-1-79dc5adf1b79@google.com
---
Brendan Jackman (2):
mm/page_alloc: Clarify terminology in migratetype fallback code
mm/page_alloc: Clarify should_claim_block() commentary
mm/compaction.c | 4 +--
mm/internal.h | 2 +-
mm/page_alloc.c | 100 ++++++++++++++++++++++++++++++--------------------------
3 files changed, 56 insertions(+), 50 deletions(-)
---
base-commit: 801d47bd96ce22acd43809bc09e004679f707c39
change-id: 20250214-clarify-steal-f244880441c1
Best regards,
--
Brendan Jackman <jackmanb@google.com>
next reply other threads:[~2025-02-28 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 9:52 Brendan Jackman [this message]
2025-02-28 9:52 ` [PATCH v4 1/2] mm/page_alloc: Clarify terminology in migratetype fallback code Brendan Jackman
2025-02-28 9:52 ` [PATCH v4 2/2] mm/page_alloc: Clarify should_claim_block() commentary Brendan Jackman
2025-02-28 9:59 ` Vlastimil Babka
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=20250228-clarify-steal-v4-0-cb2ef1a4e610@google.com \
--to=jackmanb@google.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=vbabka@suse.cz \
--cc=yosry.ahmed@linux.dev \
/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