From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andi Kleen <ak@muc.de>, Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, kkeil@suse.de
Subject: Re: [patch] tune vmalloc size
Date: Wed, 15 Sep 2004 08:07:01 -0700 [thread overview]
Message-ID: <783300000.1095260820@[10.10.2.4]> (raw)
In-Reply-To: <m34qlzbqy6.fsf@averell.firstfloor.org>
--Andi Kleen <ak@muc.de> wrote (on Wednesday, September 15, 2004 15:29:53 +0200):
> Ingo Molnar <mingo@elte.hu> writes:
>
>> there are a few devices that use lots of ioremap space. vmalloc space is
>> a showstopper problem for them.
>>
>> this patch adds the vmalloc=<size> boot parameter to override
>> __VMALLOC_RESERVE. The default is 128mb right now - e.g. vmalloc=256m
>> doubles the size.
>
> Ah, Karsten Keil did a similar patch some months ago. There is
> clearly a need.
>
> But I think this should be self tuning instead. For a machine with
> less than 900MB of memory the vmalloc area can be automagically increased,
> growing into otherwise unused address space.
>
> This way many users wouldn't need to specify weird options. So far
> most machines still don't have more than 512MB.
It already does that, IIRC.
M.
next prev parent reply other threads:[~2004-09-15 15:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2EHyq-5or-39@gated-at.bofh.it>
2004-09-15 13:29 ` Andi Kleen
2004-09-15 14:05 ` Rodrigo FGV
2004-09-15 14:12 ` Arjan van de Ven
2004-09-17 22:03 ` Chris Wedgwood
2004-09-17 22:06 ` Arjan van de Ven
2004-09-15 14:58 ` Karsten Keil
2004-09-15 15:07 ` Martin J. Bligh [this message]
2004-09-15 12:53 Ingo Molnar
2004-09-15 12:31 ` Alan Cox
2004-09-15 13:29 ` Joe Korty
2004-09-15 13:31 ` Arjan van de Ven
2004-09-15 13:40 ` Joe Korty
2004-09-15 14:14 ` Dave Jones
2004-09-15 13:40 ` Dave Jones
2004-09-15 21:33 ` Andrew Morton
2004-09-15 21:45 ` 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='783300000.1095260820@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=ak@muc.de \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®