All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonsoo Kim <js1304@gmail.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: David Rientjes <rientjes@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Michal Hocko <mhocko@kernel.org>,
	Minchan Kim <minchan@kernel.org>,
	Mel Gorman <mgorman@techsingularity.net>,
	kernel-team@lge.com, Ye Xiaolong <xiaolong.ye@intel.com>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH v2 1/2] mm/page_alloc: use ac->high_zoneidx for classzone_idx
Date: Fri, 20 Mar 2020 16:33:54 +0900	[thread overview]
Message-ID: <CAAmzW4OC56g-37SghVVsN=4tnxMwfavkK2z31abZnBh5o9J4ag@mail.gmail.com> (raw)
In-Reply-To: <9a7c94c0-c2b2-d533-316a-4fd42bdf55b1@suse.cz>

2020년 3월 19일 (목) 오후 9:21, Vlastimil Babka <vbabka@suse.cz>님이 작성:
>
> On 3/19/20 9:57 AM, Joonsoo Kim wrote:
> >> Curious: is this only an issue when vm.numa_zonelist_order is set to Node?
> >
> > Do you mean "/proc/sys/vm/numa_zonelist_order"? It looks like it's gone now.
> >
> > Thanks.
>
> Yes it's gone now, but indeed, AFAIU on older kernels with zone order instead of
> node order, this problem wouldn't manifest.

Yes. In this case, preferred_zone of an allocation is the populated highest zone
among all nodes so classzone_idx will the same.

Thanks.

  reply	other threads:[~2020-03-20  7:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18  3:32 [PATCH v2 0/2] integrate classzone_idx and high_zoneidx js1304
2020-03-18  3:32 ` [PATCH v2 1/2] mm/page_alloc: use ac->high_zoneidx for classzone_idx js1304
2020-03-18 21:29   ` David Rientjes
2020-03-18 21:29     ` David Rientjes
2020-03-19  8:57     ` Joonsoo Kim
2020-03-19  8:57       ` Joonsoo Kim
2020-03-19 12:21       ` Vlastimil Babka
2020-03-20  7:33         ` Joonsoo Kim [this message]
2020-03-20  7:33           ` Joonsoo Kim
2020-03-19 12:29   ` Vlastimil Babka
2020-03-18  3:32 ` [PATCH v2 2/2] mm/page_alloc: integrate classzone_idx and high_zoneidx js1304
2020-03-18  3:42   ` Joonsoo Kim
2020-03-18  3:42     ` Joonsoo Kim
2020-03-19 12:32   ` Vlastimil Babka
2020-03-20  7:40     ` Joonsoo Kim
2020-03-20  7:40       ` Joonsoo Kim

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='CAAmzW4OC56g-37SghVVsN=4tnxMwfavkK2z31abZnBh5o9J4ag@mail.gmail.com' \
    --to=js1304@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=kernel-team@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@kernel.org \
    --cc=minchan@kernel.org \
    --cc=rientjes@google.com \
    --cc=vbabka@suse.cz \
    --cc=xiaolong.ye@intel.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.