From: Michal Hocko <mhocko@kernel.org>
To: Wei Yang <richard.weiyang@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: vbabka@suse.cz, mgorman@techsingularity.net, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/page_alloc: return 0 in case this node has no page within the zone
Date: Wed, 22 Feb 2017 09:49:47 +0100 [thread overview]
Message-ID: <20170222084947.GE5753@dhcp22.suse.cz> (raw)
In-Reply-To: <20170209135929.GA59297@WeideMacBook-Pro.local>
On Thu 09-02-17 21:59:29, Wei Yang wrote:
> On Tue, Feb 07, 2017 at 04:41:21PM +0100, Michal Hocko wrote:
> >On Tue 07-02-17 23:32:47, Wei Yang wrote:
> >> On Tue, Feb 07, 2017 at 10:45:57AM +0100, Michal Hocko wrote:
> >[...]
> >> >Is there any reason why for_each_mem_pfn_range cannot be changed to
> >> >honor the given start/end pfns instead? I can imagine that a small zone
> >> >would see a similar pointless iterations...
> >> >
> >>
> >> Hmm... No special reason, just not thought about this implementation. And
> >> actually I just do the similar thing as in zone_spanned_pages_in_node(), in
> >> which also return 0 when there is no overlap.
> >>
> >> BTW, I don't get your point. You wish to put the check in
> >> for_each_mem_pfn_range() definition?
> >
> >My point was that you are handling one special case (an empty zone) but
> >the underlying problem is that __absent_pages_in_range might be wasting
> >cycles iterating over memblocks that are way outside of the given pfn
> >range. At least this is my understanding. If you fix that you do not
> >need the special case, right?
> >--
> >Michal Hocko
> >SUSE Labs
>
> > Not really, sorry, this area is full of awkward and subtle code when new
> > changes build on top of previous awkwardness/surprises. Any cleanup
> > would be really appreciated. That is the reason I didn't like the
> > initial check all that much.
>
> Looks my fetchmail failed to get your last reply. So I copied it here.
>
> Yes, the change here looks not that nice, while currently this is what I can't
> come up with.
THen I will suggest dropping this patch from the mmotm tree because it
doesn't sound like a big improvement and I would encourage you or
anybody else to take a deeper look and unclutter this area to be more
readable and better maintainable.
--
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-02-22 8:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 15:43 Wei Yang
2017-02-06 23:29 ` Andrew Morton
2017-02-07 15:07 ` Wei Yang
2017-02-07 9:45 ` Michal Hocko
2017-02-07 15:32 ` Wei Yang
2017-02-07 15:41 ` Michal Hocko
2017-02-08 14:05 ` Wei Yang
2017-02-08 14:39 ` Michal Hocko
2017-02-09 13:59 ` Wei Yang
2017-02-22 8:49 ` Michal Hocko [this message]
2017-02-22 10:51 ` Wei Yang
2017-02-22 11:45 ` Michal Hocko
2017-02-22 14:18 ` Wei Yang
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=20170222084947.GE5753@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=richard.weiyang@gmail.com \
--cc=vbabka@suse.cz \
/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