From: Valdis.Kletnieks@vt.edu
To: Szabolcs Szakacsits <szaka@f-secure.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Hugh Dickins <hugh@veritas.com>,
linux-kernel@vger.kernel.org
Subject: Re: scheduler went mad?
Date: Thu, 12 Apr 2001 18:24:15 -0400 [thread overview]
Message-ID: <200104122224.f3CMOFB08457@foo-bar-baz.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 13 Apr 2001 01:02:21 +0200." <Pine.LNX.4.30.0104130009350.19377-100000@fs131-224.f-secure.com>
In-Reply-To: <Pine.LNX.4.30.0104130009350.19377-100000@fs131-224.f-secure.com>
[-- Attachment #1: Type: text/plain, Size: 538 bytes --]
On Fri, 13 Apr 2001 01:02:21 +0200, Szabolcs Szakacsits said:
> Not __alloc_pages() calls oom_kill() however do_page_fault(). Not the
> same. After the system tried *really* hard to get *one* free page and
> couldn't managed why loop forever? To eat CPU and waiting for
For what it's worth, this *IS NOT* the case I'm getting bit by:
While kswapd was hung, I already had (from /proc/meminfo)
MemFree: 34064 kB
I suspect that kswapd is getting hung spinning on some *specific*
requirement that it's falling short on?
/Valdis
[-- Attachment #2: Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2001-04-12 22:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-12 14:57 Valdis.Kletnieks
2001-04-12 15:12 ` Alan Cox
2001-04-12 15:44 ` Valdis.Kletnieks
2001-04-12 18:31 ` Valdis.Kletnieks
2001-04-12 15:43 ` Hugh Dickins
2001-04-12 16:02 ` Alan Cox
2001-04-12 16:29 ` Rik van Riel
2001-04-12 15:08 ` Marcelo Tosatti
2001-04-12 15:10 ` Marcelo Tosatti
2001-04-12 18:18 ` Szabolcs Szakacsits
2001-04-12 17:56 ` Rik van Riel
2001-04-12 20:12 ` Szabolcs Szakacsits
2001-04-12 20:18 ` Rik van Riel
2001-04-12 23:02 ` Szabolcs Szakacsits
2001-04-12 22:24 ` Valdis.Kletnieks [this message]
2001-04-12 16:53 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2001-04-11 14:24 Priit Randla
2001-04-11 18:46 ` Josh McKinney
2001-04-12 15:46 ` 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=200104122224.f3CMOFB08457@foo-bar-baz.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=riel@conectiva.com.br \
--cc=szaka@f-secure.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®