From: SeongJae Park <sj@kernel.org>
To: Honggyu Kim <honggyu.kim@sk.com>
Cc: SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Steven Rostedt <rostedt@goodmis.org>,
Gregory Price <gregory.price@memverge.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, 42.hyeyoo@gmail.com,
art.jeongseob@gmail.com, kernel_team@skhynix.com,
Hyeongtak Ji <hyeongtak.ji@sk.com>, Rakie Kim <rakie.kim@sk.com>,
Yunjeong Mun <yunjeong.mun@sk.com>,
damon@lists.linux.dev
Subject: Re: [PATCH 0/8] DAMON based tiered memory management for CXL memory
Date: Thu, 13 Jun 2024 06:56:49 -0700 [thread overview]
Message-ID: <20240613135649.26707-1-sj@kernel.org> (raw)
In-Reply-To: <20240613132730.650-1-honggyu.kim@sk.com>
On Thu, 13 Jun 2024 22:27:26 +0900 Honggyu Kim <honggyu.kim@sk.com> wrote:
> On Thu, 13 Jun 2024 22:17:31 +0900 Honggyu Kim <honggyu.kim@sk.com> wrote:
> > There was an RFC IDEA "DAMOS-based Tiered-Memory Management" previously
> > posted at [1].
> >
> > It says there is no implementation of the demote/promote DAMOS action
> > are made. This patch series is about its implementation for physical
> > address space so that this scheme can be applied in system wide level.
> >
> > Changes from RFC v4:
> > https://lore.kernel.org/20240512175447.75943-1-sj@kernel.org
> > 1. Add usage and design documents
> > 2. Rename alloc_demote_folio to alloc_migrate_folio
> > 3. Add evaluation results with "demotion_enabled" true
> > 4. Rebase based on v6.10-rc3
>
> Sorry for making confusion, I didn't add "PATCH v5" tag for this patch
> series so please ignore and see the resent one.
Thank you for clarifying this.
Nonetheless, I don't mine resetting the version number of a patchset after
dropping RFC. Actually, I personally rather prefer resetting the version
number. Anyway, I don't care that much. Please use any way that you feel more
comfortable :) Please just keep the number monotonically increase.
Thanks,
SJ
>
> Honggyu
prev parent reply other threads:[~2024-06-13 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 13:17 [PATCH 0/8] DAMON based tiered memory management for CXL memory Honggyu Kim
2024-06-13 13:17 ` [PATCH 1/8] mm: make alloc_demote_folio externally invokable for migration Honggyu Kim
2024-06-13 13:17 ` [PATCH 2/8] mm: rename alloc_demote_folio to alloc_migrate_folio Honggyu Kim
2024-06-13 13:17 ` [PATCH 3/8] mm/damon/sysfs-schemes: add target_nid on sysfs-schemes Honggyu Kim
2024-06-13 13:17 ` [PATCH 4/8] mm/migrate: add MR_DAMON to migrate_reason Honggyu Kim
2024-06-13 13:17 ` [PATCH 5/8] mm/damon/paddr: introduce DAMOS_MIGRATE_COLD action for demotion Honggyu Kim
2024-06-13 13:27 ` [PATCH 0/8] DAMON based tiered memory management for CXL memory Honggyu Kim
2024-06-13 13:56 ` SeongJae Park [this message]
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=20240613135649.26707-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=art.jeongseob@gmail.com \
--cc=damon@lists.linux.dev \
--cc=gregory.price@memverge.com \
--cc=honggyu.kim@sk.com \
--cc=hyeongtak.ji@sk.com \
--cc=kernel_team@skhynix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rakie.kim@sk.com \
--cc=rostedt@goodmis.org \
--cc=yunjeong.mun@sk.com \
/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).