linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Galbraith <mikeg@weiden.de>
To: Ingo Molnar <mingo@chiara.csoma.elte.hu>
Cc: MM mailing list <linux-mm@kvack.org>,
	linux-kernel <linux-kernel@vger.rutgers.edu>
Subject: Re: [patch] zoned-2.3.28-K2 [ramdisk OOM]
Date: Wed, 17 Nov 1999 05:18:33 +0100 (CET)	[thread overview]
Message-ID: <Pine.Linu.4.10.9911170454270.418-100000@mikeg.weiden.de> (raw)
In-Reply-To: <Pine.LNX.4.10.9911161329430.3924-100000@chiara.csoma.elte.hu>

On Tue, 16 Nov 1999, Ingo Molnar wrote:

> 
> the latest patchset is at:
> 
> 	http://www.redhat.com/~mingo/zoned-2.3.28-K2
> 
> this patch is supposed to fix all known problems (including the 16MB kept
> free thing), let me know if there is still something left.

Hi Ingo,

I ran into an OOM problem while testing.  Having heard someone mention
ramdisk troubles, I enabled it and booted with ramdisk_size=16384. Made
an fs (mke2fs /dev/ram0) mounted it and ran Bonnie -s 12 a few times.
Result was terminal OOM.  Everything else seems to work fine, so this
may just be a driver bug(?).  I can't revert my tree just yet to find
out for sure.

Memleak results with line numbers translated to zoned-2.3.28-K2 stock.

buffer.c:1054: 15698 13710 15260 DELTA: 28970
filemap.c:1852: 3430 3448 3921 DELTA: 7369
slab.c:507: 468 173 142 DELTA: 315

	-Mike

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/

  reply	other threads:[~1999-11-17  4:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-16 13:18 [patch] zoned-2.3.28-K2 Ingo Molnar
1999-11-17  4:18 ` Mike Galbraith [this message]
1999-11-17 10:07   ` [patch] zoned-2.3.28-K2 [ramdisk OOM] Russell King

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=Pine.Linu.4.10.9911170454270.418-100000@mikeg.weiden.de \
    --to=mikeg@weiden.de \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=mingo@chiara.csoma.elte.hu \
    /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