linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: JoonSoo Kim <js1304@gmail.com>
To: Russell King <rmk+kernel@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-arm-kernel@lists.infradead.org,
	Joonsoo Kim <js1304@gmail.com>
Subject: Re: [PATCH v2 0/3] introduce static_vm for ARM-specific static mapped area
Date: Fri, 7 Dec 2012 01:18:16 +0900	[thread overview]
Message-ID: <CAAmzW4Ng8S_O4SEoANCWz3jsW3h3ucGSM9=Ld-n9aLuHcdgprw@mail.gmail.com> (raw)
In-Reply-To: <1354033730-850-1-git-send-email-js1304@gmail.com>

2012/11/28 Joonsoo Kim <js1304@gmail.com>:
> In current implementation, we used ARM-specific flag, that is,
> VM_ARM_STATIC_MAPPING, for distinguishing ARM specific static mapped area.
> The purpose of static mapped area is to re-use static mapped area when
> entire physical address range of the ioremap request can be covered
> by this area.
>
> This implementation causes needless overhead for some cases.
> For example, assume that there is only one static mapped area and
> vmlist has 300 areas. Every time we call ioremap, we check 300 areas for
> deciding whether it is matched or not. Moreover, even if there is
> no static mapped area and vmlist has 300 areas, every time we call
> ioremap, we check 300 areas in now.
>
> If we construct a extra list for static mapped area, we can eliminate
> above mentioned overhead.
> With a extra list, if there is one static mapped area,
> we just check only one area and proceed next operation quickly.
>
> In fact, it is not a critical problem, because ioremap is not frequently
> used. But reducing overhead is better idea.
>
> Another reason for doing this work is for removing architecture dependency
> on vmalloc layer. I think that vmlist and vmlist_lock is internal data
> structure for vmalloc layer. Some codes for debugging and stat inevitably
> use vmlist and vmlist_lock. But it is preferable that they are used
> as least as possible in outside of vmalloc.c
>
> Changelog
> v1->v2:
>   [2/3]: patch description is improved.
>   Rebased on v3.7-rc7
>
> Joonsoo Kim (3):
>   ARM: vmregion: remove vmregion code entirely
>   ARM: static_vm: introduce an infrastructure for static mapped area
>   ARM: mm: use static_vm for managing static mapped areas
>
>  arch/arm/include/asm/mach/static_vm.h |   51 ++++++++
>  arch/arm/mm/Makefile                  |    2 +-
>  arch/arm/mm/ioremap.c                 |   69 ++++-------
>  arch/arm/mm/mm.h                      |   10 --
>  arch/arm/mm/mmu.c                     |   55 +++++----
>  arch/arm/mm/static_vm.c               |   97 ++++++++++++++++
>  arch/arm/mm/vmregion.c                |  205 ---------------------------------
>  arch/arm/mm/vmregion.h                |   31 -----
>  8 files changed, 208 insertions(+), 312 deletions(-)
>  create mode 100644 arch/arm/include/asm/mach/static_vm.h
>  create mode 100644 arch/arm/mm/static_vm.c
>  delete mode 100644 arch/arm/mm/vmregion.c
>  delete mode 100644 arch/arm/mm/vmregion.h
>
> --
> 1.7.9.5
>

Hello, Russell.

Could you review this patchset, please?
I send another patchset to mm community on top of this.
That one is related to this patchset,
so I want to get a review about this patchset :)

Thanks.

  parent reply	other threads:[~2012-12-06 16:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27 16:28 [PATCH v2 0/3] introduce static_vm for ARM-specific static mapped area Joonsoo Kim
2012-11-27 16:28 ` [PATCH v2 1/3] ARM: vmregion: remove vmregion code entirely Joonsoo Kim
2012-11-27 16:28 ` [PATCH v2 2/3] ARM: static_vm: introduce an infrastructure for static mapped area Joonsoo Kim
2012-11-27 16:28 ` [PATCH v2 3/3] ARM: mm: use static_vm for managing static mapped areas Joonsoo Kim
2012-12-06 16:18 ` JoonSoo Kim [this message]
2012-12-12 14:34   ` [PATCH v2 0/3] introduce static_vm for ARM-specific static mapped area JoonSoo Kim

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='CAAmzW4Ng8S_O4SEoANCWz3jsW3h3ucGSM9=Ld-n9aLuHcdgprw@mail.gmail.com' \
    --to=js1304@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    /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).