From: js1304@gmail.com (Joonsoo Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/3] introduce static_vm for ARM-specific static mapped area
Date: Thu, 15 Nov 2012 01:55:51 +0900 [thread overview]
Message-ID: <1352912154-16210-1-git-send-email-js1304@gmail.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.
We unnecessarily iterate vmlist for finding matched area even if there
is no static mapped area. And if there are some static mapped areas,
iterating whole vmlist is not preferable.
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 outside
of vmalloc.c as least as possible.
In the near future, I will try to remove other architecture dependency on
vmalloc layer.
This is just RFC patch and I did compile-test only.
If you have any good suggestion, please let me know.
These are based on v3.7-rc5.
Thanks.
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
next reply other threads:[~2012-11-14 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 16:55 Joonsoo Kim [this message]
2012-11-14 16:55 ` [RFC PATCH 1/3] ARM: vmregion: remove vmregion code entirely Joonsoo Kim
2012-11-14 16:55 ` [RFC PATCH 2/3] ARM: static_vm: introduce an infrastructure for static mapped area Joonsoo Kim
2012-11-14 16:55 ` [RFC PATCH 3/3] ARM: mm: use static_vm for managing static mapped areas Joonsoo Kim
2012-11-14 17:39 ` [RFC PATCH 0/3] introduce static_vm for ARM-specific static mapped area Russell King - ARM Linux
2012-11-15 13:22 ` 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=1352912154-16210-1-git-send-email-js1304@gmail.com \
--to=js1304@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).