From: Voluspa <lista4@comhem.se>
To: kernel@kolivas.org
Cc: akpm@osdl.org, nickpiggin@yahoo.com.au, mr@ramendik.ru,
linux-kernel@vger.kernel.org
Subject: Sv: Re: 2.6.10-rc3: kswapd eats CPU on start of memory-eating task
Date: Sun, 19 Dec 2004 15:02:17 +0100 (MET) [thread overview]
Message-ID: <4416624.1103464937664.JavaMail.tomcat@pne-ps4-sn2> (raw)
On 2004-12-18 23:02:33 Con Kolivas wrote:
> Try disabling the swap token
>
> echo 0 > /proc/sys/vm/swap_token_timeout
Hi Con. It changes the behaviour of my testcase, yes, but it doesn't cure the
problem. When swap_token_timeout is the default 300 the screen freezes are
longer in duration, about 30 seconds. With a swap_token_timeout of 0, max
screen freezeis about 10 seconds, inter-foliated with freezes of less length.
On a positive note, the _total_ time of "unstability" is equal in both cases.
Wh
ich in my animation test means 6 minutes. I said 3 previously, but that was
wrong. Didn't let it run long enough.
Cheers,
Mats Johannesson
reply other threads:[~2004-12-19 14:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4416624.1103464937664.JavaMail.tomcat@pne-ps4-sn2 \
--to=lista4@comhem.se \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mr@ramendik.ru \
--cc=nickpiggin@yahoo.com.au \
/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