summaryrefslogtreecommitdiffstats
path: root/arch/arm/mm/fsr-2level.c
diff options
context:
space:
mode:
authorJoonsoo Kim <js1304@gmail.com>2013-02-09 06:28:06 +0100
committerRussell King <rmk+kernel@arm.linux.org.uk>2013-02-16 18:54:22 +0100
commit101eeda38c0ab8a4f916176e325d9e036d981a24 (patch)
tree874b1f0002c9153e6af28b1ec3dd6aa0e7737086 /arch/arm/mm/fsr-2level.c
parentARM: 7645/1: ioremap: introduce an infrastructure for static mapped area (diff)
downloadlinux-101eeda38c0ab8a4f916176e325d9e036d981a24.tar.xz
linux-101eeda38c0ab8a4f916176e325d9e036d981a24.zip
ARM: 7646/1: mm: use static_vm for managing static mapped areas
A static mapped area is ARM-specific, so it is better not to use generic vmalloc data structure, that is, vmlist and vmlist_lock for managing static mapped area. And it causes some needless overhead and reducing this overhead is better idea. Now, we have newly introduced static_vm infrastructure. With it, we don't need to iterate all mapped areas. Instead, we just iterate static mapped areas. It helps to reduce an overhead of finding matched area. And architecture dependency on vmalloc layer is removed, so it will help to maintainability for vmalloc layer. Reviewed-by: Nicolas Pitre <nico@linaro.org> Acked-by: Rob Herring <rob.herring@calxeda.com> Tested-by: Santosh Shilimkar <santosh.shilimkar@ti.com> Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'arch/arm/mm/fsr-2level.c')
0 files changed, 0 insertions, 0 deletions