linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: David Hildenbrand <david@redhat.com>
Cc: Qi Zheng <zhengqi.arch@bytedance.com>,
	Qi Zheng <arch0.zheng@gmail.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, Teng Hu <huteng.ht@bytedance.com>,
	Matthew Wilcox <willy@infradead.org>,
	Mel Gorman <mgorman@techsingularity.net>,
	Oscar Salvador <osalvador@suse.de>,
	Muchun Song <muchun.song@linux.dev>
Subject: Re: [PATCH] mm: page_alloc: don't allocate page from memoryless nodes
Date: Tue, 14 Feb 2023 13:44:06 +0200	[thread overview]
Message-ID: <Y+t0Bhu7BCzH2Dp4@kernel.org> (raw)
In-Reply-To: <4386151c-0328-d207-9a71-933ef61817f9@redhat.com>

(added x86 folks)

On Tue, Feb 14, 2023 at 12:29:42PM +0100, David Hildenbrand wrote:
> On 14.02.23 12:26, Qi Zheng wrote:
> > On 2023/2/14 19:22, David Hildenbrand wrote:
> > > 
> > > TBH, this is the first time I hear of NODE_MIN_SIZE and it seems to be a
> > > pretty x86 specific thing.
> > > 
> > > Are we sure we want to get NODE_MIN_SIZE involved?
> > 
> > Maybe add an arch_xxx() to handle it?
> 
> I still haven't figured out what we want to achieve with NODE_MIN_SIZE at
> all. It smells like an arch-specific hack looking at
> 
> "Don't confuse VM with a node that doesn't have the minimum amount of
> memory"
> 
> Why shouldn't mm-core deal with that?

Well, a node with <4M RAM is not very useful and bears all the overhead of
an extra live node.

But, hey, why won't we just drop that '< NODE_MIN_SIZE' and let people with
weird HW configurations just live with this?
 
> I'd appreciate an explanation of the bigger picture, what the issue is and
> what the approach to solve it is (including memory onlining/offlining).
> 
> -- 
> Thanks,
> 
> David / dhildenb
> 

-- 
Sincerely yours,
Mike.


  parent reply	other threads:[~2023-02-14 11:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-12 11:03 [PATCH] mm: page_alloc: don't allocate page from memoryless nodes Qi Zheng
2023-02-13  8:47 ` Vlastimil Babka
2023-02-13 11:00   ` Qi Zheng
2023-02-14  8:42     ` Vlastimil Babka
2023-02-14  9:17       ` David Hildenbrand
2023-02-14  9:43         ` Mike Rapoport
     [not found]           ` <67240e55-af49-f20a-2b4b-b7d574cd910d@gmail.com>
2023-02-14 11:22             ` David Hildenbrand
2023-02-14 11:26               ` Qi Zheng
2023-02-14 11:29                 ` David Hildenbrand
2023-02-14 11:38                   ` Qi Zheng
2023-02-14 11:44                   ` Mike Rapoport [this message]
2023-02-14 11:48                     ` David Hildenbrand
2023-02-14 11:58                       ` David Hildenbrand
2023-02-14 12:09                         ` [External] " Qi Zheng
2023-02-14 13:38                         ` Michal Hocko
2023-02-15  9:30                           ` Mike Rapoport
2023-02-15  9:41                             ` Qi Zheng
2023-02-15 10:08                               ` Mike Rapoport
2023-02-15 10:19                                 ` Qi Zheng
2023-02-15  9:43                             ` David Hildenbrand
2023-02-15 10:04                               ` Mike Rapoport
2023-02-15 10:11                                 ` David Hildenbrand
2023-02-15 16:55                             ` Michal Hocko
2023-10-16  4:09                             ` Qi Zheng
2023-10-17  6:12                               ` Mike Rapoport
2023-02-14 12:33                     ` Qi Zheng
2023-02-14 12:46                     ` Mike Rapoport
     [not found]   ` <Y+tQDN/TmdTPFFR6@kernel.org>
2023-02-14 10:33     ` Qi Zheng

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=Y+t0Bhu7BCzH2Dp4@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=arch0.zheng@gmail.com \
    --cc=david@redhat.com \
    --cc=huteng.ht@bytedance.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=muchun.song@linux.dev \
    --cc=osalvador@suse.de \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.org \
    --cc=zhengqi.arch@bytedance.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).