From: Ingo Molnar <mingo@elte.hu>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Xiao Guangrong <ericxiao.gr@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Jens Axboe <jens.axboe@oracle.com>,
Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, x86@kernel.org,
Jeremy Fitzhardinge <jeremy@goop.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86: reuse the boot-time mappings of fixed_addresses
Date: Mon, 31 Aug 2009 10:26:32 +0200 [thread overview]
Message-ID: <20090831082632.GB15619@elte.hu> (raw)
In-Reply-To: <4A997088.60908@zytor.com>
* H. Peter Anvin <hpa@zytor.com> wrote:
> Ingo Molnar wrote:
>> * Xiao Guangrong <ericxiao.gr@gmail.com> wrote:
>>
>>> From: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
>>>
>>> Some fixed_addresses items are only used when system boot, after
>>> boot, they are free but no way to use, like early ioremap area. They
>>> are wasted for us, we can reuse them after system boot.
>>>
>>> In this patch, we put them in permanent kmap's area and expand
>>> vmalloc's address range. In boot time, reserve them in
>>> permanent_kmaps_init() to avoid multiple used, after system boot, we
>>> unreserved them then user can use it.
>>>
>>> Signed-off-by: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
>>> ---
>>> arch/x86/include/asm/fixmap.h | 2 ++
>>> arch/x86/include/asm/pgtable_32_types.h | 4 ++--
>>> arch/x86/mm/init_32.c | 8 ++++++++
>>> include/linux/highmem.h | 2 ++
>>> mm/highmem.c | 26 ++++++++++++++++++++++++++
>>> 5 files changed, 40 insertions(+), 2 deletions(-)
>>
>> I'm wondering, how much space do we save this way, on a typical bootup
>> on a typical PC?
>>
>
> Not a huge lot... a few dozen pages.
I guess it's still worth doing - what do you think?
Ingo
--
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:[~2009-08-31 8:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 2:35 Xiao Guangrong
2009-08-29 11:00 ` Ingo Molnar
2009-08-29 18:16 ` H. Peter Anvin
2009-08-31 8:26 ` Ingo Molnar [this message]
2009-09-01 0:29 ` Jeremy Fitzhardinge
2009-09-04 7:33 ` Ingo Molnar
2009-09-04 15:47 ` Jeremy Fitzhardinge
2009-09-04 16:15 ` H. Peter Anvin
2009-09-04 18:55 ` Ingo Molnar
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=20090831082632.GB15619@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=ericxiao.gr@gmail.com \
--cc=hpa@zytor.com \
--cc=jens.axboe@oracle.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xiaoguangrong@cn.fujitsu.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