Re: [External] Re: [PATCH 3/3] mm/page_alloc: Fix typo in debug info of calculate_node_totalpages

2018-05-09 Thread Michal Hocko
On Sat 05-05-18 02:10:35, Huaisheng HS1 Ye wrote: [...] > But this printk is a relatively meaningful reference within dmesg log. > Especially for people who doesn't have much experience, or someone > has a plan to modify boundary of zones within free_area_init_*. Could you be more specific

Re: [External] Re: [PATCH 3/3] mm/page_alloc: Fix typo in debug info of calculate_node_totalpages

2018-05-09 Thread Michal Hocko
On Sat 05-05-18 02:10:35, Huaisheng HS1 Ye wrote: [...] > But this printk is a relatively meaningful reference within dmesg log. > Especially for people who doesn't have much experience, or someone > has a plan to modify boundary of zones within free_area_init_*. Could you be more specific

RE: [External] Re: [PATCH 3/3] mm/page_alloc: Fix typo in debug info of calculate_node_totalpages

2018-05-04 Thread Huaisheng HS1 Ye
> On Fri 04-05-18 14:52:09, Huaisheng Ye wrote: > > realtotalpages is calculated by taking off absent_pages from > > spanned_pages in every zone. > > Debug message of calculate_node_totalpages shall accurately > > indicate that it is real totalpages to avoid ambiguity. > > Is the printk actually

RE: [External] Re: [PATCH 3/3] mm/page_alloc: Fix typo in debug info of calculate_node_totalpages

2018-05-04 Thread Huaisheng HS1 Ye
> On Fri 04-05-18 14:52:09, Huaisheng Ye wrote: > > realtotalpages is calculated by taking off absent_pages from > > spanned_pages in every zone. > > Debug message of calculate_node_totalpages shall accurately > > indicate that it is real totalpages to avoid ambiguity. > > Is the printk actually