From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Daniel Phillips <phillips@bonn-fries.net>
Subject: Re: VM in 2.4.7-pre hurts...
Date: Sat, 07 Jul 2001 17:34:04 -0400 [thread overview]
Message-ID: <3B47804C.77B7329A@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0107071828500.1389-100000@duckman.distro.conectiva>
Rik van Riel wrote:
>
> On Sat, 7 Jul 2001, Alan Cox wrote:
>
> > > instead. That way the vmstat output might be more useful, although vmstat
> > > obviously won't know about the new "SwapCache:" field..
> > >
> > > Can you try that, and see if something else stands out once the misleading
> > > accounting is taken care of?
> >
> > Its certainly misleading. I got Jeff to try making oom return
> > 4999 out of 5000 times regardless.
>
> In that case, he _is_ OOM. ;)
>
> 1) (almost) no free memory
> 2) no free swap
> 3) very little pagecache + buffer cache
It got -considerably- farther after Alan's suggested hack to the OOM
killer; so at least in this instance, OOM killer appeared to me to be
killing too early...
--
Jeff Garzik | A recent study has shown that too much soup
Building 1024 | can cause malaise in laboratory mice.
MandrakeSoft |
next prev parent reply other threads:[~2001-07-07 21:34 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-07 13:41 VM in 2.4.7-pre hurts Jeff Garzik
2001-07-07 14:05 ` Jeff Garzik
2001-07-07 17:28 ` Linus Torvalds
2001-07-07 17:37 ` Jeff Garzik
2001-07-07 17:53 ` Linus Torvalds
2001-07-07 18:08 ` Jeff Garzik
2001-07-07 18:11 ` Rik van Riel
2001-07-07 21:33 ` Alan Cox
2001-07-07 18:00 ` Rik van Riel
2001-07-07 21:25 ` Alan Cox
2001-07-07 21:29 ` Rik van Riel
2001-07-07 21:34 ` Jeff Garzik [this message]
2001-07-07 21:43 ` Alan Cox
2001-07-07 21:45 ` Rik van Riel
[not found] <Pine.LNX.4.33L.0107071542420.17825-100000@duckman.distro.conectiva>
2001-07-07 18:54 ` Linus Torvalds
2001-07-07 20:11 ` Rik van Riel
2001-07-08 17:11 ` Linus Torvalds
2001-07-08 18:29 ` Rik van Riel
[not found] <Pine.LNX.4.33.0107081640570.308-100000@mikeg.weiden.de>
2001-07-08 15:43 ` Rik van Riel
2001-07-08 17:15 ` Mike Galbraith
2001-07-08 17:58 ` Linus Torvalds
2001-07-08 18:23 ` Rik van Riel
2001-07-08 19:30 ` Linus Torvalds
2001-07-09 2:59 ` Linus Torvalds
2001-07-10 2:56 ` Andrea Arcangeli
2001-07-10 4:03 ` Linus Torvalds
2001-07-10 4:20 ` Linus Torvalds
2001-07-10 5:43 ` Andrea Arcangeli
2001-07-10 14:56 ` Andrea Arcangeli
2001-07-10 18:46 ` Linus Torvalds
2001-07-10 5:11 ` Andrea Arcangeli
2001-07-09 7:56 ` Mike Galbraith
2001-07-09 8:25 ` Christoph Rohland
2001-07-09 9:18 ` Mike Galbraith
2001-07-09 9:29 ` Christoph Rohland
2001-07-09 9:38 ` Mike Galbraith
2001-07-09 11:17 ` Mike Galbraith
2001-07-09 11:30 ` Christoph Rohland
2001-07-09 12:26 ` Mike Galbraith
2001-07-09 11:25 ` Christoph Rohland
2001-07-09 12:20 ` Mike Galbraith
2001-07-09 16:20 ` Linus Torvalds
2001-07-09 19:44 ` Christoph Rohland
2001-07-09 20:46 ` Linus Torvalds
2001-07-11 19:39 ` Christoph Rohland
2001-07-11 1:05 ` Marcelo Tosatti
2001-07-11 4:03 ` Mike Galbraith
2001-07-12 5:00 ` David Lang
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=3B47804C.77B7329A@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.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.