public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: jmerkey@comcast.net
Cc: linux-kernel@vger.kernel.org, jmerkey@drdos.com
Subject: Re: 2.6.8.1 mempool subsystem sickness
Date: Thu, 09 Sep 2004 09:05:03 +1000	[thread overview]
Message-ID: <413F901F.5020901@yahoo.com.au> (raw)
In-Reply-To: <090820041648.7817.413F37F600049F4800001E892200762302970A059D0A0306@comcast.net>

jmerkey@comcast.net wrote:
> On a system with 4GB of memory, and without 
> the user space patch that spilts user space
> just a stock kernel, I am seeing memory 
> allocation failures with X server and simple
> apps on a machine with a Pentium 4 
> processor and 500MB of memory.  
> 
> If you load large apps and do a lot of 
> skb traffic, the mempool abd slab 
> caches start gobbling up pages
> and don't seem to balance them 
> very well, resulting in memory 
> allocation failures over time if
> the system stays up for a week 
> or more.  
> 
> I am also seeing the same behavior 
> on another system which has been
> running for almost 30 days with 
> an skb based traffic regeneration 
> test calling and sending skb's
> in kernel between two interfaces.
> 
> The pages over time get stuck 
> in the slab allocator and user
> space apps start to fail on alloc
> requests.  
> 
> Rebooting the system clears
> the problem, which slowly over time
> comes back.  I am seeing this with
> stock kernels from kernel.org 
> and on kernels I have patched,
> so the problem seems to be
> in the base code.  I have spent
> the last two weeks observing 
> the problem to verify I can
> reproduce it and it keeps 
> happening.  
> 
> Jeff
> 

Hi Jeff,
Can you give us a few more details please? Post the allocation failure
messages in full, and post /proc/meminfo, etc. Thanks.

  reply	other threads:[~2004-09-08 23:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-08 16:48 2.6.8.1 mempool subsystem sickness jmerkey
2004-09-08 23:05 ` Nick Piggin [this message]
     [not found] <091420042058.15928.41475B8000002BA100003E382200763704970A059D0A0306@comcast.net>
2004-09-14 20:32 ` 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

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=413F901F.5020901@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=jmerkey@comcast.net \
    --cc=jmerkey@drdos.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox