linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@linux.ibm.com>
To: Ohhoon Kwon <ohoono.kwon@samsung.com>
Cc: david@redhat.com, akpm@linux-foundation.org, mhocko@suse.com,
	bhe@redhat.com, ohkwon1043@gmail.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] mm: sparse: remove __section_nr() function
Date: Fri, 2 Jul 2021 15:58:02 +0300	[thread overview]
Message-ID: <YN8NWgf5yTHbsVlG@linux.ibm.com> (raw)
In-Reply-To: <20210702094132.6276-1-ohoono.kwon@samsung.com>

On Fri, Jul 02, 2021 at 06:41:29PM +0900, Ohhoon Kwon wrote:
> This series contains cleanups to remove __section_nr().
> 
> When CONFIG_SPARSEMEM_EXTREME is enabled, __section_nr() could be
> costly since it iterates all section roots to check if the given
> mem_section is in its range.
> 
> On the other hand, __nr_to_section which converts section_nr to
> mem_section can be done in O(1).
> 
> The only users of __section_nr() was section_mark_present() and
> find_memory_block().
> 
> PATCH 1 & 2 changes both functions to use section_nr instead of
> mem_section.
> PATCH 3 finally removes __section_nr() function.
> 
> More details can be found in each changelogs.
> 
> Ohhoon Kwon (3):
>   mm: sparse: pass section_nr to section_mark_present
>   mm: sparse: pass section_nr to find_memory_block
>   mm: sparse: remove __section_nr() function
> 
>  .../platforms/pseries/hotplug-memory.c        |  4 +--
>  drivers/base/memory.c                         |  4 +--
>  include/linux/memory.h                        |  2 +-
>  include/linux/mmzone.h                        |  1 -
>  mm/sparse.c                                   | 35 +++----------------
>  5 files changed, 9 insertions(+), 37 deletions(-)
> 
> -- 
> 2.17.1
 
For the series:

Acked-by: Mike Rapoport <rppt@linux.ibm.com>

-- 
Sincerely yours,
Mike.

      parent reply	other threads:[~2021-07-02 12:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210702094457epcas1p295611b5799befffd016b8fccf3adceff@epcas1p2.samsung.com>
2021-07-02  9:41 ` [PATCH 0/3] mm: sparse: remove __section_nr() function Ohhoon Kwon
     [not found]   ` <CGME20210702094457epcas1p3ddac76bd3cc3e5b93fadb897cdb6dfd0@epcas1p3.samsung.com>
2021-07-02  9:41     ` [PATCH 1/3] mm: sparse: pass section_nr to section_mark_present Ohhoon Kwon
2021-07-02 12:13       ` Michal Hocko
2021-07-02 17:54       ` David Hildenbrand
     [not found]   ` <CGME20210702094457epcas1p40fba85e22861cf1cc85a085719030c24@epcas1p4.samsung.com>
2021-07-02  9:41     ` [PATCH 2/3] mm: sparse: pass section_nr to find_memory_block Ohhoon Kwon
2021-07-02 12:17       ` Michal Hocko
2021-07-02 17:55       ` David Hildenbrand
     [not found]   ` <CGME20210702094457epcas1p4e181c7b0a18338403a7ffb57f44807fe@epcas1p4.samsung.com>
2021-07-02  9:41     ` [PATCH 3/3] mm: sparse: remove __section_nr() function Ohhoon Kwon
2021-07-02 12:18       ` Michal Hocko
2021-07-02 17:57         ` David Hildenbrand
2021-07-02 12:58   ` Mike Rapoport [this message]

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=YN8NWgf5yTHbsVlG@linux.ibm.com \
    --to=rppt@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=ohkwon1043@gmail.com \
    --cc=ohoono.kwon@samsung.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;
as well as URLs for NNTP newsgroup(s).