damon.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>, SeongJae Park <sj@kernel.org>
Cc: <damon@lists.linux.dev>, <linux-mm@kvack.org>,
	<vishal.moola@gmail.com>, <willy@infradead.org>,
	<david@redhat.com>, Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: [PATCH -next v4 0/8] mm: convert page_idle/damon to use folios
Date: Fri, 30 Dec 2022 15:08:41 +0800	[thread overview]
Message-ID: <20221230070849.63358-1-wangkefeng.wang@huawei.com> (raw)

v4:
- correct some wrong spell pointed by SeongJae
- add new folio_memcg_check() from Matthew and use it in patch0005
- add RBs

v3:
- more thoroughly converting in page_idle_get_folio() suggested by Matthew
  also do it in damon_get_folio().
- address some commets from SeongJae

v2:
- drop unsafe pfn_to_online_folio(), convert page_idle_get_page() and 
  damon_get_page() to return a folio after grab a reference
- convert damon hugetlb related functions
- rebased on next-20221226.


Kefeng Wang (7):
  mm: page_idle: convert page idle to use a folio
  mm/damon: introduce damon_get_folio()
  mm/damon: convert damon_ptep/pmdp_mkold() to use a folio
  mm/damon/paddr: convert damon_pa_*() to use a folio
  mm/damon/vaddr: convert damon_young_pmd_entry() to use a folio
  mm/damon: remove unneeded damon_get_page()
  mm/damon/vaddr: convert hugetlb related functions to use a folio

Matthew Wilcox (1):
  mm: memcg: Add folio_memcg_check()

 include/linux/memcontrol.h | 40 +++++++++++++++++---------
 mm/damon/ops-common.c      | 38 ++++++++++++++-----------
 mm/damon/ops-common.h      |  2 +-
 mm/damon/paddr.c           | 58 +++++++++++++++++---------------------
 mm/damon/vaddr.c           | 38 ++++++++++++-------------
 mm/memcontrol.c            |  6 ++--
 mm/page_idle.c             | 47 +++++++++++++++---------------
 7 files changed, 120 insertions(+), 109 deletions(-)

-- 
2.35.3


             reply	other threads:[~2022-12-30  6:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30  7:08 Kefeng Wang [this message]
2022-12-30  7:08 ` [PATCH -next v4 1/8] mm: memcg: Add folio_memcg_check() Kefeng Wang
2022-12-30  7:08 ` [PATCH -next v4 2/8] mm: page_idle: convert page idle to use a folio Kefeng Wang
2022-12-30  7:08 ` [PATCH -next v4 3/8] mm/damon: introduce damon_get_folio() Kefeng Wang
2022-12-30  7:08 ` [PATCH -next v4 4/8] mm/damon: convert damon_ptep/pmdp_mkold() to use a folio Kefeng Wang
2022-12-30  7:08 ` [PATCH -next v4 5/8] mm/damon/paddr: convert damon_pa_*() " Kefeng Wang
2022-12-30  7:08 ` [PATCH -next v4 6/8] mm/damon/vaddr: convert damon_young_pmd_entry() " Kefeng Wang
2022-12-30  7:08 ` [PATCH -next v4 7/8] mm/damon: remove unneeded damon_get_page() Kefeng Wang
2022-12-30  7:08 ` [PATCH -next v4 8/8] mm/damon/vaddr: convert hugetlb related functions to use a folio Kefeng 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=20221230070849.63358-1-wangkefeng.wang@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=damon@lists.linux.dev \
    --cc=david@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=sj@kernel.org \
    --cc=vishal.moola@gmail.com \
    --cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).