From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@digeo.com>, Dave Hansen <haveblue@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] add vmalloc stats to meminfo
Date: Sun, 15 Sep 2002 07:50:19 -0700 [thread overview]
Message-ID: <73286230.1032076218@[10.10.2.3]> (raw)
In-Reply-To: <3D84340A.25ED4C69@digeo.com>
>> Some workloads like to eat up a lot of vmalloc space.
>
> Which workloads are those?
>
>> It is often hard to tell
>> whether this is because the area is too small, or just too fragmented. This
>> makes it easy to determine.
>
> I do not recall ever having seen any bug/problem reports which this patch
> would have helped to solve. Could you explain in more detai why is it useful?
Seen on specweb - doubling the size of the vmalloc space made it go
away, but without any counters, it was all really just guesswork.
I am also going to implement per-node slabcache on top of vmalloc,
as slabs have to be in permanently mapped KVA, but all ZONE_NORMAL
is on node 0. That's going to put a lot of pressure on the vmalloc
area.
M.
--
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/
next prev parent reply other threads:[~2002-09-15 14:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-15 6:03 Dave Hansen
2002-09-15 7:17 ` Andrew Morton
2002-09-15 7:11 ` William Lee Irwin III
2002-09-15 7:17 ` William Lee Irwin III
2002-09-15 17:23 ` M. Edward (Ed) Borasky
2002-09-15 17:26 ` William Lee Irwin III
2002-09-15 17:44 ` M. Edward Borasky
2002-09-15 14:50 ` Martin J. Bligh [this message]
2002-09-16 5:30 ` Matt Porter
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='73286230.1032076218@[10.10.2.3]' \
--to=mbligh@aracnet.com \
--cc=akpm@digeo.com \
--cc=haveblue@us.ibm.com \
--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