From: Andrew Morton <akpm@digeo.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] add vmalloc stats to meminfo
Date: Sun, 15 Sep 2002 00:17:30 -0700 [thread overview]
Message-ID: <3D84340A.25ED4C69@digeo.com> (raw)
In-Reply-To: 3D8422BB.5070104@us.ibm.com
Dave Hansen wrote:
>
> 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?
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@digeo.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] add vmalloc stats to meminfo
Date: Sun, 15 Sep 2002 00:17:30 -0700 [thread overview]
Message-ID: <3D84340A.25ED4C69@digeo.com> (raw)
In-Reply-To: 3D8422BB.5070104@us.ibm.com
Dave Hansen wrote:
>
> 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?
--
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 6:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-15 6:03 [PATCH] add vmalloc stats to meminfo Dave Hansen
2002-09-15 7:17 ` Andrew Morton [this message]
2002-09-15 7:17 ` Andrew Morton
2002-09-15 7:11 ` William Lee Irwin III
2002-09-15 7:11 ` William Lee Irwin III
2002-09-15 7:17 ` 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:23 ` M. Edward (Ed) Borasky
2002-09-15 17:26 ` William Lee Irwin III
2002-09-15 17:26 ` William Lee Irwin III
2002-09-15 17:44 ` M. Edward Borasky
2002-09-15 17:44 ` M. Edward Borasky
2002-09-15 14:50 ` Martin J. Bligh
2002-09-15 14:50 ` Martin J. Bligh
2002-09-16 5:30 ` Matt Porter
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=3D84340A.25ED4C69@digeo.com \
--to=akpm@digeo.com \
--cc=Martin.Bligh@us.ibm.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 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.