All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, ziy@nvidia.com,
	zhongjiang-ali@linux.alibaba.com, weixugc@google.com,
	shy828301@gmail.com, shakeelb@google.com, riel@surriel.com,
	osalvador@suse.de, mhocko@suse.com, mgorman@techsingularity.net,
	hasanalmaruf@fb.com, feng.tang@intel.com,
	dave.hansen@linux.intel.com, baolin.wang@linux.alibaba.com,
	ying.huang@intel.com
Subject: Re: + numa-balancing-optimize-page-placement-for-memory-tiering-system.patch added to -mm tree
Date: Wed, 2 Feb 2022 11:19:26 +0100	[thread overview]
Message-ID: <20220202101926.GY20638@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20220201222010.E9F39C340EB@smtp.kernel.org>

On Tue, Feb 01, 2022 at 02:20:10PM -0800, Andrew Morton wrote:
> 
> The patch titled
>      Subject: NUMA balancing: optimize page placement for memory tiering system
> has been added to the -mm tree.  Its filename is
>      numa-balancing-optimize-page-placement-for-memory-tiering-system.patch
> 
> This patch should soon appear at
>     https://ozlabs.org/~akpm/mmots/broken-out/numa-balancing-optimize-page-placement-for-memory-tiering-system.patch
> and later at
>     https://ozlabs.org/~akpm/mmotm/broken-out/numa-balancing-optimize-page-placement-for-memory-tiering-system.patch
> 
> Before you just go and hit "reply", please:
>    a) Consider who else should be cc'ed
>    b) Prefer to cc a suitable mailing list as well
>    c) Ideally: find the original patch on the mailing list and do a
>       reply-to-all to that, adding suitable additional cc's
> 
> *** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
> 
> The -mm tree is included into linux-next and is updated
> there every 3-4 working days
> 
> ------------------------------------------------------
> From: Huang Ying <ying.huang@intel.com>
> Subject: NUMA balancing: optimize page placement for memory tiering system

I'm thinking this is a bit soon, current stuff is all sorts of broken
in the presence of memory only nodes.

I *really* want to see all that fixed before we merge this stuff.

  reply	other threads:[~2022-02-02 10:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 22:20 + numa-balancing-optimize-page-placement-for-memory-tiering-system.patch added to -mm tree Andrew Morton
2022-02-02 10:19 ` Peter Zijlstra [this message]
2022-02-07  8:32   ` Huang, Ying
2022-02-22  2:45 Andrew Morton

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=20220202101926.GY20638@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=feng.tang@intel.com \
    --cc=hasanalmaruf@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@suse.com \
    --cc=mm-commits@vger.kernel.org \
    --cc=osalvador@suse.de \
    --cc=riel@surriel.com \
    --cc=shakeelb@google.com \
    --cc=shy828301@gmail.com \
    --cc=weixugc@google.com \
    --cc=ying.huang@intel.com \
    --cc=zhongjiang-ali@linux.alibaba.com \
    --cc=ziy@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.