From: Joe Korty <joe.korty@ccur.com>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] tune vmalloc size
Date: Wed, 15 Sep 2004 09:40:47 -0400 [thread overview]
Message-ID: <20040915134047.GA30493@tsunami.ccur.com> (raw)
In-Reply-To: <20040915133144.GB30530@devserv.devel.redhat.com>
On Wed, Sep 15, 2004 at 03:31:44PM +0200, Arjan van de Ven wrote:
> On Wed, Sep 15, 2004 at 09:29:36AM -0400, Joe Korty wrote:
> > On Wed, Sep 15, 2004 at 02:53:56PM +0200, Ingo Molnar wrote:
> > >
> > > 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.
> >
> > Perhaps this should instead be a configurable.
>
> boot time settable is 100x better than only compile time settable imo :)
IMO, everything that is changable at boot time needs an equivalent way
of changing the default without specifying a boot time value.
boot time values works well only when the number of values that need
changing is small.
Joe
next prev parent reply other threads:[~2004-09-15 13:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 12:53 [patch] tune vmalloc size 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 [this message]
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
[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
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=20040915134047.GA30493@tsunami.ccur.com \
--to=joe.korty@ccur.com \
--cc=akpm@osdl.org \
--cc=arjanv@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.