* Re: [PATCH] mm: Fix a typo in __next_mem_pfn_range() comments.
[not found] ` <20181107150312.GH27423@dhcp22.suse.cz>
@ 2018-11-08 3:08 ` cc
0 siblings, 0 replies; only message in thread
From: cc @ 2018-11-08 3:08 UTC (permalink / raw)
To: mhocko
Cc: rppt, akpm, rppt, pasha.tatashin, Jonathan Corbet, stefan, malat,
neelx, andriy.shevchenko, linux-mm, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1895 bytes --]
Thanks for all your replies,i am a newbie here.
Michal Hocko <mhocko@suse.com> 于2018年11月7日周三 下午11:03写道:
> On Wed 07-11-18 16:37:05, Mike Rapoport wrote:
> > On Wed, Nov 07, 2018 at 03:13:06PM +0100, Michal Hocko wrote:
> > > On Wed 07-11-18 15:54:22, Mike Rapoport wrote:
> > > > On Wed, Nov 07, 2018 at 11:25:49AM +0100, Michal Hocko wrote:
> > > > > On Wed 07-11-18 18:02:47, Chen Chang wrote:
> > > > > > mm: Fix a typo in __next_mem_pfn_range() comments.
> > > > >
> > > > > those two names are just too similar. And I wouldn't be surprised
> if
> > > > > there was a considerable overlap in functionality which just asks
> for
> > > > > a unification. In a separate patch of course.
> > > >
> > > > There is an overlap, but I'm not sure if the unification is straight
> > > > forward. The for_each_mem_pfn_range() is really simple iterator,
> while
> > > > for_each_mem_range() has additional logic based on memblock flags.
> > >
> > > Is there any reason we cannot emulate the former by later by type_b =
> > > NULL and flags=0?
> >
> > Mostly. There's a hotplug related check:
> >
> > /* skip hotpluggable memory regions if needed */
> > if (movable_node_is_enabled() && memblock_is_hotpluggable(m))
> > continue;
> >
> > in __next_mem_range() that is not related to flags and type_b and I don't
> > understand hotplug enough to tell.
> >
> > Maybe this check can become
> >
> > /* skip hotpluggable memory regions if needed */
> > if ((flags & MEMBLOCK_HOTPLUG) && movable_node_is_enabled() &&
> > memblock_is_hotpluggable(m))
> > continue;
> >
> > and then using flags=0 and type_b=NULL would be possible.
>
> OK, let's discuss this in a separate thread. A simlification in this
> area is always welcome ;)
>
> --
> Michal Hocko
> SUSE Labs
>
[-- Attachment #2: Type: text/html, Size: 2522 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-11-08 3:08 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20181107100247.13359-1-rainccrun@gmail.com>
[not found] ` <20181107102549.GB27423@dhcp22.suse.cz>
[not found] ` <20181107135421.GA5638@rapoport-lnx>
[not found] ` <20181107141306.GF27423@dhcp22.suse.cz>
[not found] ` <20181107143703.GB5638@rapoport-lnx>
[not found] ` <20181107150312.GH27423@dhcp22.suse.cz>
2018-11-08 3:08 ` [PATCH] mm: Fix a typo in __next_mem_pfn_range() comments cc
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox