linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org, zhongjiang@huawei.com
Subject: Re: [patch 13/15] mm/page_owner: align with pageblock_nr pages
Date: Fri, 1 Dec 2017 18:15:17 +0100	[thread overview]
Message-ID: <20171201171517.lyqukuvuh4cswnla@dhcp22.suse.cz> (raw)
In-Reply-To: <8c2af1ab-e64f-21da-f295-ea1ead343206@suse.cz>

On Fri 01-12-17 17:58:28, Vlastimil Babka wrote:
> On 11/30/2017 11:15 PM, akpm@linux-foundation.org wrote:
> > From: zhong jiang <zhongjiang@huawei.com>
> > Subject: mm/page_owner: align with pageblock_nr pages
> > 
> > When pfn_valid(pfn) returns false, pfn should be aligned with
> > pageblock_nr_pages other than MAX_ORDER_NR_PAGES in init_pages_in_zone,
> > because the skipped 2M may be valid pfn, as a result, early allocated
> > count will not be accurate.
> > 
> > Link: http://lkml.kernel.org/r/1468938136-24228-1-git-send-email-zhongjiang@huawei.com
> > Signed-off-by: zhong jiang <zhongjiang@huawei.com>
> > Cc: Michal Hocko <mhocko@kernel.org>
> > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> 
> The author never responded and Michal Hocko basically NAKed it in
> https://lkml.kernel.org/r/<20160812130727.GI3639@dhcp22.suse.cz>
> I think we should drop it.

Or extend the changelog to actually describe what kind of problem it
fixes and do an additional step to unigy
MAX_ORDER_NR_PAGES/pageblock_nr_pages
 
> > ---
> > 
> >  mm/page_owner.c |    2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff -puN mm/page_owner.c~mm-page_owner-align-with-pageblock_nr-pages mm/page_owner.c
> > --- a/mm/page_owner.c~mm-page_owner-align-with-pageblock_nr-pages
> > +++ a/mm/page_owner.c
> > @@ -544,7 +544,7 @@ static void init_pages_in_zone(pg_data_t
> >  	 */
> >  	for (; pfn < end_pfn; ) {
> >  		if (!pfn_valid(pfn)) {
> > -			pfn = ALIGN(pfn + 1, MAX_ORDER_NR_PAGES);
> > +			pfn = ALIGN(pfn + 1, pageblock_nr_pages);
> >  			continue;
> >  		}
> >  
> > _
> > 
> > --
> > To unsubscribe, send a message with 'unsubscribe linux-mm' in
> > the body to majordomo@kvack.org.  For more info on Linux MM,
> > see: http://www.linux-mm.org/ .
> > Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
> > 

-- 
Michal Hocko
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2017-12-01 17:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30 22:15 akpm
2017-12-01 16:58 ` Vlastimil Babka
2017-12-01 17:15   ` Michal Hocko [this message]
2017-12-04 11:51     ` zhong jiang
2017-12-04 12:01       ` Michal Hocko
2017-12-04 12:23         ` zhong jiang
2017-12-04 12:35           ` Michal Hocko
2017-12-04 12:56             ` zhong jiang
2017-12-05 11:22               ` Vlastimil Babka
2017-12-05 11:47                 ` Vlastimil Babka
2017-12-05 12:50                 ` zhong jiang
2017-12-06  8:18                   ` Vlastimil Babka

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=20171201171517.lyqukuvuh4cswnla@dhcp22.suse.cz \
    --to=mhocko@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=vbabka@suse.cz \
    --cc=zhongjiang@huawei.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