public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: Andi Kleen <ak@muc.de>, Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, kkeil@suse.de
Subject: Re: [patch] tune vmalloc size
Date: Sat, 18 Sep 2004 00:06:13 +0200	[thread overview]
Message-ID: <20040917220613.GA16920@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040917220340.GA2890@taniwha.stupidest.org>

[-- Attachment #1: Type: text/plain, Size: 501 bytes --]

On Fri, Sep 17, 2004 at 03:03:40PM -0700, Chris Wedgwood wrote:
> On Wed, Sep 15, 2004 at 04:12:56PM +0200, Arjan van de Ven wrote:
> 
> > that is the case already
> 
> why do we still use 128MB as a default then?  this is way over-kill
> from what i can tell looking on what my machines use.  i'd rather have
> this be a bit smaller and enable the slab/whatever to grow a little
> more

if you have an old glibc it will use ldt's which in turn use vmalloc for
threading... 128Mb is no luxury there.


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-09-17 22:13 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 ` [patch] tune vmalloc size 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 [this message]
2004-09-15 14:58   ` Karsten Keil
2004-09-15 15:07   ` Martin J. Bligh
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=20040917220613.GA16920@devserv.devel.redhat.com \
    --to=arjanv@redhat.com \
    --cc=ak@muc.de \
    --cc=cw@f00f.org \
    --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