From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
To: Russell King <linux@arm.linux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, js1304@gmail.com,
Will Deacon <will.deacon@arm.com>,
Nicolas Pitre <nico@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: [PATCH v3 0/3] introduce static_vm for ARM-specific static mapped area
Date: Thu, 24 Jan 2013 10:28:51 +0900 [thread overview]
Message-ID: <1358990934-4893-1-git-send-email-iamjoonsoo.kim@lge.com> (raw)
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 vm_struct list management,
entirely. For more information, look at the following link.
http://lkml.org/lkml/2012/12/6/184
Changelog
v2->v3:
coverletter: refer a link related to this work
[2/3]: drop @flags of find_static_vm_vaddr
Rebased on v3.8-rc4
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 | 54 +++++----
arch/arm/mm/static_vm.c | 94 +++++++++++++++
arch/arm/mm/vmregion.c | 205 ---------------------------------
arch/arm/mm/vmregion.h | 31 -----
8 files changed, 204 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
next reply other threads:[~2013-01-24 1:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 1:28 Joonsoo Kim [this message]
2013-01-24 1:28 ` [PATCH v3 1/3] ARM: vmregion: remove vmregion code entirely Joonsoo Kim
2013-01-29 23:36 ` Nicolas Pitre
2013-01-24 1:28 ` [PATCH v3 2/3] ARM: static_vm: introduce an infrastructure for static mapped area Joonsoo Kim
2013-01-30 0:05 ` Nicolas Pitre
2013-01-30 7:36 ` Joonsoo Kim
2013-01-24 1:28 ` [PATCH v3 3/3] ARM: mm: use static_vm for managing static mapped areas Joonsoo Kim
2013-01-30 0:06 ` Nicolas Pitre
2013-01-28 17:51 ` [PATCH v3 0/3] introduce static_vm for ARM-specific static mapped area Will Deacon
2013-01-28 18:04 ` Nicolas Pitre
2013-01-29 6:56 ` Joonsoo Kim
2013-01-29 23:35 ` Nicolas Pitre
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=1358990934-4893-1-git-send-email-iamjoonsoo.kim@lge.com \
--to=iamjoonsoo.kim@lge.com \
--cc=catalin.marinas@arm.com \
--cc=js1304@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nico@linaro.org \
--cc=will.deacon@arm.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).