linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <porter@cox.net>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Andrew Morton <akpm@zip.com.au>,
	"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 22:30:04 -0700	[thread overview]
Message-ID: <20020915223004.A17831@home.com> (raw)
In-Reply-To: <3D8422BB.5070104@us.ibm.com>; from haveblue@us.ibm.com on Sat, Sep 14, 2002 at 11:03:39PM -0700

On Sat, Sep 14, 2002 at 11:03:39PM -0700, Dave Hansen wrote:
> Some workloads like to eat up a lot of vmalloc space.  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.

Great, I was going to do something nearly the same to help out
with debugging high-end embedded applications.  It is quite common
for us to see multiple PCI masters with PCI memory windows in sizes
ranging from 256MB-1GB that are being ioremapped and consuming
vmalloc space (along with all the other consumers).  I'd love to
see this in the kernel since it would make it much easier to debug
some folks' custom board ports when they show symptoms of running
out of vmalloc space (i.e. modules not loading).

Regards,
-- 
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
--
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/

      parent reply	other threads:[~2002-09-16  5:30 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
2002-09-16  5:30 ` Matt Porter [this message]

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=20020915223004.A17831@home.com \
    --to=porter@cox.net \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=akpm@zip.com.au \
    --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