From: Michal Hocko <mhocko@suse.com>
To: zhong jiang <zhongjiang@huawei.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [patch 13/15] mm/page_owner: align with pageblock_nr pages
Date: Mon, 4 Dec 2017 13:35:46 +0100 [thread overview]
Message-ID: <20171204123546.lhhcbpulihz3upm6@dhcp22.suse.cz> (raw)
In-Reply-To: <5A253E55.7040706@huawei.com>
On Mon 04-12-17 20:23:49, zhong jiang wrote:
> On 2017/12/4 20:01, Michal Hocko wrote:
> > On Mon 04-12-17 19:51:12, zhong jiang wrote:
> >> On 2017/12/2 1:15, Michal Hocko wrote:
> >>> 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
> >>>
> >> Hi, Michal
> >>
> >> IIRC, I had explained the reason for patch. if it not. I am so sorry for that.
> >>
> >> when we select MAX_ORDER_NR_PAGES, the second 2M will be skiped.
> >> it maybe result in normal pages leak.
> >>
> >> meanwhile. as you had said. it make the code consistent. why do not we do it.
> >>
> >> I think it is reasonable to upstream the patch. maybe I should rewrite the changelog
> >> and repost it.
> >>
> >> Michal, Do you think ?
> > Yes, rewrite the patch changelog and make it _clear_ what it fixes and
> > under _what_ conditions. There are also other places using
> > MAX_ORDER_NR_PAGES rathern than pageblock_nr_pages. Do they need to be
> > updated as well?
> in the lastest kernel. according to correspond context, I can not find the candidate. :-)
git grep says some in page_ext.c, memory_hotplug.c and few in the arch
code. I belive we really want to describe and document the distinction
between the two constants and explain when to use which one.
--
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>
next prev parent reply other threads:[~2017-12-04 12:35 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
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 [this message]
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=20171204123546.lhhcbpulihz3upm6@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