From: Andrew Morton <akpm@osdl.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: riel@redhat.com, kernel@kolivas.org, mr@ramendik.ru,
akpm@digeo.com, lista4@comhem.se, linux-kernel@vger.kernel.org
Subject: Re: 2.6.10-rc3: kswapd eats CPU on start of memory-eating task
Date: Sun, 19 Dec 2004 23:07:54 -0800 [thread overview]
Message-ID: <20041219230754.64c0e52e.akpm@osdl.org> (raw)
In-Reply-To: <1103517225.5093.12.camel@npiggin-nld.site>
Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>
> On Sun, 2004-12-19 at 22:21 -0500, Rik van Riel wrote:
> > On Mon, 20 Dec 2004, Con Kolivas wrote:
> >
> > > I still suspect the thrash token patch even with the swap token timeout
> > > at 0. Is it completely disabled at 0 or does it still do something?
> >
> > It makes it harder to page out pages from the task holding the
> > token. I wonder if kswapd should try to steal the token away
> > from the task holding it, so in effect nobody holds the token
> > when the system isn't under a heavy swapping load.
> >
>
> In that case, the first thing we need to do is disable thrash token
> completely, and retest that. We still don't know for sure that it is
> the problem.
>
> I don't have the code in front of me at the moment, but I'll be able
> to send a patch to do that in a couple of hours, if nobody beats me
> to it.
This should disable the thrashing control code?
--- 25/mm/rmap.c~a 2004-12-19 23:05:58.759420936 -0800
+++ 25-akpm/mm/rmap.c 2004-12-19 23:06:43.105679280 -0800
@@ -395,6 +395,8 @@ int page_referenced(struct page *page, i
{
int referenced = 0;
+ ignore_token = 1;
+
if (page_test_and_clear_young(page))
referenced++;
_
next prev parent reply other threads:[~2004-12-20 8:03 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 22:40 2.6.10-rc3: kswapd eats CPU on start of memory-eating task 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 [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 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-14 7:24 Voluspa
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=20041219230754.64c0e52e.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=akpm@digeo.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lista4@comhem.se \
--cc=mr@ramendik.ru \
--cc=nickpiggin@yahoo.com.au \
--cc=riel@redhat.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.