All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: "Jeff V. Merkey" <jmerkey@drdos.com>,
	jmerkey@galt.devicelogics.com, linux-kernel@vger.kernel.org,
	jmerkey@comcast.net
Subject: Re: 2.6.8.1 mempool subsystem sickness
Date: Thu, 16 Sep 2004 07:56:51 +0200	[thread overview]
Message-ID: <20040916055650.GE2300@suse.de> (raw)
In-Reply-To: <4148F059.9060100@yahoo.com.au>

On Thu, Sep 16 2004, Nick Piggin wrote:
> Jeff V. Merkey wrote:
> >Jeff
> >
> >Here's the stats from the test of the patch against 2.6.8-rc2 with the 
> >patch applied
> >
> >
> 
> Scanning stats look good at a quick glance. kswapd doesn't seem to be
> going crazy.
> 
> However,
> size-65536         32834  32834  65536    1   16
> 
> This slab entry is taking up about 2GB of unreclaimable memory (order-4,
> no less). This must be a leak... does the number continue to rise as
> your system runs?

There's also a huge amount of 16-page bio + vecs in flight:

biovec-16         131340

That would point to a leak as well, most likely.

-- 
Jens Axboe


  reply	other threads:[~2004-09-16  6:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <091420042058.15928.41475B8000002BA100003E382200763704970A059D0A0306@comcast.net>
2004-09-14 20:32 ` 2.6.8.1 mempool subsystem sickness Jeff V. Merkey
2004-09-14 22:59   ` Nick Piggin
     [not found]     ` <20040914223122.GA3325@galt.devicelogics.com>
2004-09-14 23:51       ` Nick Piggin
2004-09-15  0:51         ` Gene Heskett
2004-09-15 17:27         ` Jeff V. Merkey
2004-09-15 17:33           ` Jeff V. Merkey
2004-09-16  1:46           ` Nick Piggin
2004-09-16  5:56             ` Jens Axboe [this message]
2004-09-08 16:48 jmerkey
2004-09-08 23:05 ` Nick Piggin

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=20040916055650.GE2300@suse.de \
    --to=axboe@suse.de \
    --cc=jmerkey@comcast.net \
    --cc=jmerkey@drdos.com \
    --cc=jmerkey@galt.devicelogics.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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.