linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Gregory Price <gregory.price@memverge.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: Matthew Wilcox <willy@infradead.org>,
	Gregory Price <gourry.memverge@gmail.com>,
	linux-mm@kvack.org, akpm@linux-foundation.org, david@redhat.com,
	vbabka@suse.cz, naoya.horiguchi@linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] kpageflags: respect folio head-page flag placement
Date: Wed, 8 Nov 2023 18:33:13 -0500	[thread overview]
Message-ID: <ZUwauTb/MqvyUEfI@memverge.com> (raw)
In-Reply-To: <cc4ac7de-97f5-4131-804d-622fb158dba9@huawei.com>

On Wed, Nov 08, 2023 at 10:01:19AM +0800, Kefeng Wang wrote:
> 
> Yes, I see your "Node Weights and Weighted Interleave", this is an
> interesting topic, we need some easy and efficient way to use tiered
> memory.
> 

There will be an LPC talk on it next week in the CXL track, presented
by another group that's been testing it.  Please tune in!

> > 
> > There's only a handful, so yeah the best way is probably to go ahead and
> > swap k = page->flags for k = *folio_flags(folio, 0) and then handle the
> > couple of outliars.
> 
> If you don't mind, I maybe try to convert it in my changes.
> 

Please feel free! I am happy to help test, CC me on subsequent patches
please!

~Gregory


  reply	other threads:[~2023-11-08 23:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30 18:00 Gregory Price
2023-10-30 23:22 ` Matthew Wilcox
2023-10-30 23:41   ` Gregory Price
2023-10-31  9:13     ` Matthew Wilcox
2023-10-31  4:34       ` Gregory Price
2023-11-07  1:03         ` Kefeng Wang
2023-11-07 15:34           ` Gregory Price
2023-11-08  2:01             ` Kefeng Wang
2023-11-08 23:33               ` Gregory Price [this message]
2023-11-09  9:05                 ` 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=ZUwauTb/MqvyUEfI@memverge.com \
    --to=gregory.price@memverge.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=gourry.memverge@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=naoya.horiguchi@linux.dev \
    --cc=vbabka@suse.cz \
    --cc=wangkefeng.wang@huawei.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