public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: akpm@linux-foundation.org
Cc: baolin.wang@linux.alibaba.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] Some small improvements for compaction
Date: Tue, 10 Jan 2023 21:36:17 +0800	[thread overview]
Message-ID: <cover.1673342761.git.baolin.wang@linux.alibaba.com> (raw)

Hi,

When I did some compaction testing, I found some small rooms to improve
as well as some code cleanups. Please help to review. Thanks.

Baolin Wang (5):
  mm: compaction: Remove redundant VM_BUG_ON() in compact_zone()
  mm: compaction: Move list validation into compact_zone()
  mm: compaction: Count the migration scaned pages events for proactive
    compaction
  mm: compaction: Add missing kcompactd wakeup trace event
  mm: compaction: Avoid fragmentation score calculation for empty zones

 mm/compaction.c | 25 +++++++++++--------------
 1 file changed, 11 insertions(+), 14 deletions(-)

-- 
2.27.0


             reply	other threads:[~2023-01-10 13:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10 13:36 Baolin Wang [this message]
2023-01-10 13:36 ` [PATCH 1/5] mm: compaction: Remove redundant VM_BUG_ON() in compact_zone() Baolin Wang
2023-01-10 13:37   ` Matthew Wilcox
2023-01-10 23:25     ` Andrew Morton
2023-01-10 23:37       ` Matthew Wilcox
2023-01-11  6:40         ` Baolin Wang
2023-01-11 21:51           ` Andrew Morton
2023-01-10 13:36 ` [PATCH 2/5] mm: compaction: Move list validation into compact_zone() Baolin Wang
2023-01-10 13:36 ` [PATCH 3/5] mm: compaction: Count the migration scanned pages events for proactive compaction Baolin Wang
2023-01-10 13:36 ` [PATCH 4/5] mm: compaction: Add missing kcompactd wakeup trace event Baolin Wang
2023-01-10 13:36 ` [PATCH 5/5] mm: compaction: Avoid fragmentation score calculation for empty zones Baolin Wang

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=cover.1673342761.git.baolin.wang@linux.alibaba.com \
    --to=baolin.wang@linux.alibaba.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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