RE: [RFC PATCH 5/5] mm, page_alloc: Introduce ZONELIST_FALLBACK_SAME_TYPE fallback list

2019-04-25 Thread Du, Fan
.@alibaba-inc.com; Huang, Ying >; linux...@kvack.org; linux-kernel@vger.kernel.org >Subject: Re: [RFC PATCH 5/5] mm, page_alloc: Introduce >ZONELIST_FALLBACK_SAME_TYPE fallback list > >On Thu 25-04-19 08:20:28, Du, Fan wrote: >> >> >> >-Original Message

Re: [RFC PATCH 5/5] mm, page_alloc: Introduce ZONELIST_FALLBACK_SAME_TYPE fallback list

2019-04-25 Thread Michal Hocko
tion.org; Wu, Fengguang ; > >Williams, Dan J ; Hansen, Dave > >; xishi.qiuxi...@alibaba-inc.com; Huang, Ying > >; linux...@kvack.org; linux-kernel@vger.kernel.org > >Subject: Re: [RFC PATCH 5/5] mm, page_alloc: Introduce > >ZONELIST_FALLBACK_SAME_TYPE fallback l

RE: [RFC PATCH 5/5] mm, page_alloc: Introduce ZONELIST_FALLBACK_SAME_TYPE fallback list

2019-04-25 Thread Du, Fan
.@alibaba-inc.com; Huang, Ying >; linux...@kvack.org; linux-kernel@vger.kernel.org >Subject: Re: [RFC PATCH 5/5] mm, page_alloc: Introduce >ZONELIST_FALLBACK_SAME_TYPE fallback list > >On Thu 25-04-19 07:55:58, Du, Fan wrote: >> >> PMEM is good for frequently read

Re: [RFC PATCH 5/5] mm, page_alloc: Introduce ZONELIST_FALLBACK_SAME_TYPE fallback list

2019-04-25 Thread Michal Hocko
On Thu 25-04-19 07:55:58, Du, Fan wrote: > >> PMEM is good for frequently read accessed page, e.g. page cache(implicit > >> page > >> request), or user space data base (explicit page request) > >> For now this patch create GFP_SAME_NODE_TYPE for such cases, additional > >> Implementation will be

RE: [RFC PATCH 5/5] mm, page_alloc: Introduce ZONELIST_FALLBACK_SAME_TYPE fallback list

2019-04-25 Thread Du, Fan
.@alibaba-inc.com; Huang, Ying >; linux...@kvack.org; linux-kernel@vger.kernel.org >Subject: Re: [RFC PATCH 5/5] mm, page_alloc: Introduce >ZONELIST_FALLBACK_SAME_TYPE fallback list > >On Thu 25-04-19 07:43:09, Du, Fan wrote: >> >> >> >-Original Message

Re: [RFC PATCH 5/5] mm, page_alloc: Introduce ZONELIST_FALLBACK_SAME_TYPE fallback list

2019-04-25 Thread Michal Hocko
; Hansen, Dave > >; xishi.qiuxi...@alibaba-inc.com; Huang, Ying > >; linux...@kvack.org; linux-kernel@vger.kernel.org > >Subject: Re: [RFC PATCH 5/5] mm, page_alloc: Introduce > >ZONELIST_FALLBACK_SAME_TYPE fallback list > > > >On Thu 25-04-19 09:21:35, Fan Du wr

RE: [RFC PATCH 5/5] mm, page_alloc: Introduce ZONELIST_FALLBACK_SAME_TYPE fallback list

2019-04-25 Thread Du, Fan
t;; Huang, Ying ; >linux...@kvack.org; Linux Kernel Mailing List >Subject: Re: [RFC PATCH 5/5] mm, page_alloc: Introduce >ZONELIST_FALLBACK_SAME_TYPE fallback list > >Hi Fan Du, > >I think we should change the print in mminit_verify_zonelist too. > >This patch changes the orde

RE: [RFC PATCH 5/5] mm, page_alloc: Introduce ZONELIST_FALLBACK_SAME_TYPE fallback list

2019-04-25 Thread Du, Fan
@kvack.org; linux-kernel@vger.kernel.org >Subject: Re: [RFC PATCH 5/5] mm, page_alloc: Introduce >ZONELIST_FALLBACK_SAME_TYPE fallback list > >On Thu 25-04-19 09:21:35, Fan Du wrote: >> On system with heterogeneous memory, reasonable fall back lists woul be: >> a. No fall back

Re: [RFC PATCH 5/5] mm, page_alloc: Introduce ZONELIST_FALLBACK_SAME_TYPE fallback list

2019-04-25 Thread Michal Hocko
On Thu 25-04-19 09:21:35, Fan Du wrote: > On system with heterogeneous memory, reasonable fall back lists woul be: > a. No fall back, stick to current running node. > b. Fall back to other nodes of the same type or different type >e.g. DRAM node 0 -> DRAM node 1 -> PMEM node 2 -> PMEM node 3 >

Re: [RFC PATCH 5/5] mm, page_alloc: Introduce ZONELIST_FALLBACK_SAME_TYPE fallback list

2019-04-24 Thread Xishi Qiu
Hi Fan Du, I think we should change the print in mminit_verify_zonelist too. This patch changes the order of ZONELIST_FALLBACK, so the default numa policy can alloc DRAM first, then PMEM, right? Thanks, Xishi Qiu > On system with heterogeneous memory, reasonable fall back lists woul be: >

[RFC PATCH 5/5] mm, page_alloc: Introduce ZONELIST_FALLBACK_SAME_TYPE fallback list

2019-04-24 Thread Fan Du
On system with heterogeneous memory, reasonable fall back lists woul be: a. No fall back, stick to current running node. b. Fall back to other nodes of the same type or different type e.g. DRAM node 0 -> DRAM node 1 -> PMEM node 2 -> PMEM node 3 c. Fall back to other nodes of the same type