From: Voluspa <lista4@comhem.se>
To: mr@ramendik.ru
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10-rc3: kswapd eats CPU on start of memory-eating task
Date: Tue, 14 Dec 2004 08:24:10 +0100 (MET) [thread overview]
Message-ID: <24338756.1103009050547.JavaMail.tomcat@pne-ps1-sn1> (raw)
At 2004-12-14 2:28:59 Mikhail Ramendik wrote:
> BTW, somebody told me in a private email to try the oomkiller patch, but
I
> could not extract it from the Web archive, so I don't have the latest version
> of that :( I'd apreciate if anyone emailed that to me, or gave me a link.
or
> a pointer to instructions on getting it right from obe of the Web archives.
Final incarnation can be picked up at
http://marc.theaimsgroup.com/?l=linux-kernel&m=110269783227867&w=2
But on my machine it doesn't address the issue you speak of. When I run something
as demanding as that (end of memory, eating a large chunk of swap) it behaves
like
yours. Gkrellm stops - no screen updates, mouse becomes very unresponsive etc.
Though
I saw that as "normal" for the workload.
In this appartment there's no difference between 2.6.9 patched with the kswapd
fix and
the oomkill patch, or 2.6.10-rc3 with or without oomkill patch. Can't comment
on 2.6.8
since I didn't exhaust memory with applications back then.
Mvh
Mats Johannesson
next reply other threads:[~2004-12-14 7:24 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-14 7:24 Voluspa [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-23 0:26 Zou, Nanhai
2004-12-23 13:26 ` Rik van Riel
2004-12-23 13:28 ` Rik van Riel
2004-12-22 8:45 Zou, Nanhai
2004-12-22 14:23 ` Rik van Riel
2004-12-20 12:59 Voluspa
2004-12-21 1:46 ` Mikhail Ramendik
2004-12-20 9:22 Zou, Nanhai
2004-12-20 15:08 ` Rik van Riel
2004-12-20 6:51 Voluspa
2004-12-20 7:12 ` Andrew Morton
2004-12-20 7:44 ` Nick Piggin
2004-12-20 8:03 ` Con Kolivas
2004-12-20 8:58 ` Con Kolivas
2004-12-20 12:55 ` Andrea Arcangeli
2004-12-20 12:06 ` Ed Tomlinson
2004-12-20 12:29 ` Con Kolivas
2004-12-20 17:49 ` Hideo AOKI
2004-12-20 23:51 ` Nick Piggin
2004-12-20 9:07 ` mr
2004-12-20 15:06 ` Rik van Riel
2004-12-19 23:12 Voluspa
2004-12-19 22:40 Voluspa
2004-12-19 22:56 ` Nick Piggin
2004-12-19 23:08 ` Mikhail Ramendik
2004-12-19 23:57 ` Andrew Morton
2004-12-20 0:03 ` Mikhail Ramendik
2004-12-20 3:02 ` Con Kolivas
2004-12-20 3:21 ` Rik van Riel
2004-12-20 4:13 ` Con Kolivas
2004-12-20 4:18 ` Rik van Riel
2004-12-20 4:21 ` Con Kolivas
2004-12-20 4:33 ` Nick Piggin
2004-12-20 7:07 ` Andrew Morton
2004-12-19 14:08 Voluspa
2004-12-17 10:45 Voluspa
2004-12-18 23:02 ` Con Kolivas
2004-12-15 22:49 Voluspa
2004-12-16 8:03 ` Nick Piggin
2004-12-16 8:14 ` Nick Piggin
2004-12-15 14:02 Voluspa
2004-12-17 0:41 ` Andrew Morton
2004-12-12 14:28 Mikhail Ramendik
2004-12-14 0:51 ` Nick Piggin
2004-12-14 2:28 ` Mikhail Ramendik
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=24338756.1103009050547.JavaMail.tomcat@pne-ps1-sn1 \
--to=lista4@comhem.se \
--cc=linux-kernel@vger.kernel.org \
--cc=mr@ramendik.ru \
/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
Powered by JetHome