From: Mike Rapoport <rppt@linux.ibm.com>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>, Linux-MM <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] memblock: remove memblock_{set,clear}_region_flags
Date: Fri, 8 Feb 2019 12:04:01 +0200 [thread overview]
Message-ID: <20190208100401.GB11096@rapoport-lnx> (raw)
In-Reply-To: <CAFqt6zbvYKQS0NO3x9d45ubwf_MdEf67x1=xUHLb+ippCFmeQg@mail.gmail.com>
On Thu, Feb 07, 2019 at 10:02:24PM +0530, Souptick Joarder wrote:
> On Wed, Feb 6, 2019 at 6:01 PM Mike Rapoport <rppt@linux.ibm.com> wrote:
> >
> > The memblock API provides dedicated helpers to set or clear a flag on a
> > memory region, e.g. memblock_{mark,clear}_hotplug().
> >
> > The memblock_{set,clear}_region_flags() functions are used only by the
> > memblock internal function that adjusts the region flags.
> > Drop these functions and use open-coded implementation instead.
> >
> > Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
> > ---
> > include/linux/memblock.h | 12 ------------
> > mm/memblock.c | 9 ++++++---
> > 2 files changed, 6 insertions(+), 15 deletions(-)
> >
> > diff --git a/include/linux/memblock.h b/include/linux/memblock.h
> > index 71c9e32..32a9a6b 100644
> > --- a/include/linux/memblock.h
> > +++ b/include/linux/memblock.h
> > @@ -317,18 +317,6 @@ void __next_mem_pfn_range_in_zone(u64 *idx, struct zone *zone,
> > for_each_mem_range_rev(i, &memblock.memory, &memblock.reserved, \
> > nid, flags, p_start, p_end, p_nid)
> >
> > -static inline void memblock_set_region_flags(struct memblock_region *r,
> > - enum memblock_flags flags)
> > -{
> > - r->flags |= flags;
> > -}
> > -
> > -static inline void memblock_clear_region_flags(struct memblock_region *r,
> > - enum memblock_flags flags)
> > -{
> > - r->flags &= ~flags;
> > -}
> > -
> > #ifdef CONFIG_HAVE_MEMBLOCK_NODE_MAP
> > int memblock_set_node(phys_addr_t base, phys_addr_t size,
> > struct memblock_type *type, int nid);
> > diff --git a/mm/memblock.c b/mm/memblock.c
> > index 0151a5b..af5fe8e 100644
> > --- a/mm/memblock.c
> > +++ b/mm/memblock.c
> > @@ -851,11 +851,14 @@ static int __init_memblock memblock_setclr_flag(phys_addr_t base,
> > if (ret)
> > return ret;
> >
> > - for (i = start_rgn; i < end_rgn; i++)
> > + for (i = start_rgn; i < end_rgn; i++) {
> > + struct memblock_region *r = &type->regions[i];
>
> Is it fine if we drop this memblock_region *r altogether ?
I prefer using a local variable to
type->regions[i].flags
> > +
> > if (set)
> > - memblock_set_region_flags(&type->regions[i], flag);
> > + r->flags |= flag;
> > else
> > - memblock_clear_region_flags(&type->regions[i], flag);
> > + r->flags &= ~flag;
> > + }
> >
> > memblock_merge_regions(type);
> > return 0;
> > --
> > 2.7.4
> >
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2019-02-08 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 12:10 [PATCH 0/2] memblock: minor cleanups Mike Rapoport
2019-02-06 12:10 ` [PATCH 1/2] memblock: remove memblock_{set,clear}_region_flags Mike Rapoport
2019-02-07 16:32 ` Souptick Joarder
2019-02-08 10:04 ` Mike Rapoport [this message]
2019-02-06 12:10 ` [PATCH 2/2] memblock: split checks whether a region should be skipped to a helper function Mike Rapoport
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=20190208100401.GB11096@rapoport-lnx \
--to=rppt@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.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