From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Joonsoo Kim <js1304@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 0/3] introduce static_vm for ARM-specific static mapped area
Date: Wed, 14 Nov 2012 17:39:28 +0000 [thread overview]
Message-ID: <20121114173928.GK3290@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1352912154-16210-1-git-send-email-js1304@gmail.com>
On Thu, Nov 15, 2012 at 01:55:51AM +0900, Joonsoo Kim wrote:
> 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.
In what 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.
Why not? Please put some explanation into your message rather than
just statements making unexplained assertions.
> 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.
The vmalloc layer is also made available for ioremap use, and it is
intended that architectures hook into this for ioremap support.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-11-14 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 16:55 Joonsoo Kim
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 ` Russell King - ARM Linux [this message]
2012-11-15 13:22 ` [RFC PATCH 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=20121114173928.GK3290@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=js1304@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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