All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Jeff V. Merkey" <jmerkey@drdos.com>
Cc: 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 11:46:01 +1000	[thread overview]
Message-ID: <4148F059.9060100@yahoo.com.au> (raw)
In-Reply-To: <41487B6D.1080202@drdos.com>

Jeff V. Merkey wrote:
> Nick Piggin wrote:

>> OK, this is against 2.6.9-rc2. Let me know how you go. Thanks
>>
>>  
>>
> 
> Nick,
> 
> The problem is corrected with this patch.  I am running with 3GB of 
> kernel memory
> and 1GB user space with the userspace splitting patch with very heavy 
> swapping
> and user space app activity and no failed allocations.  This patch 
> should be rolled
> into 2.6.9-rc2 since it fixes the problem.  With standard 3GB User/1GB 
> kernel
> address space, it also fixes the problems with X server running out of 
> memory
> and the apps crashing.
> 

Hi Jeff,
Thanks, that is very cool. The memory problems you're seeing aren't
actually a regression (it's always been like that), and I still haven't
got hold of some gigabit networking hardware to test it thoroughly, so
as such so it may be difficult to get this into 2.6.9. Hopefully soon
though.

I can provide you (or anyone) with up to date patches on request though,
so just let me know.

> 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?

  parent reply	other threads:[~2004-09-16  1:46 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 [this message]
2004-09-16  5:56             ` Jens Axboe
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=4148F059.9060100@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=jmerkey@comcast.net \
    --cc=jmerkey@drdos.com \
    --cc=jmerkey@galt.devicelogics.com \
    --cc=linux-kernel@vger.kernel.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.