All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Hugh Dickins <hugh@veritas.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: overcommit stuff
Date: Sat, 21 Sep 2002 18:12:45 -0700	[thread overview]
Message-ID: <3D8D190D.2C459ABB@digeo.com> (raw)
In-Reply-To: 20020921235351.GC25605@holomorphy.com

William Lee Irwin III wrote:
> 
> On Sun, Sep 22, 2002 at 12:46:59AM +0100, Hugh Dickins wrote:
> > I don't think Alan can be held responsible for errors in the
> > overcommit stuff rml ported to 2.5 and I then added fixes to.
> > I believe it is up to date in 2.5.
> > Committed_AS certainly errs on the pessimistic side, that's
> > what it's about.  How much swap do you have i.e. is 23GB
> > committed impossible, or just surprising to you?  Does the
> > number go back to what it started off from when you kill
> > off the tests?  How are "those pages" allocated e.g. what
> > mmap args?
> > Hugh
> 
> In my case it's not really possible to rerun a test in the same
> boot. It's not really survived very often, and when it has, it
> generally fails to start a second time. Various other things feel the
> OOM sting then, e.g. kernel compiles, small task count dbench, etc.
> 
> Some of this might be slab, but I think there might be a leak.
> The best answers I've come up with thus far are "Hrm, the OOM killer
> gets set off at the wrong times, and maybe delalloc would kill bh's?"
> 

I see no leak.  After a 30-40 minute run I managed to wrestle all
the threads to the ground, unmounted the target fs and ended
up with


             total       used       free     shared    buffers     cached
Mem:       7249612      62796    7186816          0      11016      10804
-/+ buffers/cache:      40976    7208636
Swap:      3951844         80    3951764
--
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/

      reply	other threads:[~2002-09-22  1:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-21 23:27 overcommit stuff Andrew Morton
2002-09-21 23:28 ` William Lee Irwin III
2002-09-21 23:31 ` Martin J. Bligh
2002-09-22  0:03   ` Andrew Morton
2002-09-22  0:08     ` Martin J. Bligh
2002-09-22  1:04       ` Hugh Dickins
2002-09-22  1:07         ` Martin J. Bligh
2002-09-21 23:46 ` Hugh Dickins
2002-09-21 23:53   ` Andrew Morton
2002-09-22  0:49     ` Hugh Dickins
2002-09-22  1:07       ` Andrew Morton
2002-09-22  1:45         ` Hugh Dickins
2002-09-22  1:49           ` Andrew Morton
2002-09-21 23:53   ` William Lee Irwin III
2002-09-22  1:12     ` Andrew Morton [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=3D8D190D.2C459ABB@digeo.com \
    --to=akpm@digeo.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hugh@veritas.com \
    --cc=linux-mm@kvack.org \
    --cc=wli@holomorphy.com \
    /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.