From: Ed Tomlinson <edt@aei.ca>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Andrew Morton <akpm@osdl.org>,
lista4@comhem.se, linux-kernel@vger.kernel.org, mr@ramendik.ru,
kernel@kolivas.org, riel@redhat.com
Subject: Re: 2.6.10-rc3: kswapd eats CPU on start of memory-eating task
Date: Mon, 20 Dec 2004 07:06:05 -0500 [thread overview]
Message-ID: <200412200706.06534.edt@aei.ca> (raw)
In-Reply-To: <41C682F1.20200@yahoo.com.au>
On Monday 20 December 2004 02:44, Nick Piggin wrote:
> Andrew Morton wrote:
> > Voluspa <lista4@comhem.se> wrote:
> >
> >>Would be nice though if someone else could verify...
> >
> >
> > Well I'd love to, but afaik the only workloads which we currently know of
> > involve complex userspace apps which I have no experience running.
> >
> > Did anyone come up with a simple step-by-step procedure for reproducing the
> > problem? It would be good if someone could do this, because I don't think
> > we understand the root cause yet?
> >
>
> I admit to generally being in the same boat as you with respect to
> running complex userspace apps.
>
> However, based on this and other scattered reports, I'd say it seems
> quite likely that token based thrashing control is the culprit. Based
> on the cost/benefit, I wonder if we should disable TBTC by default for
> 2.6.10, rather than trying to fix it, and try again for 2.6.11?
>
> Rik? Andrew?
>
> Also, it would be nice to have a sysctl to *completely* disable TBTC,
> that would make testing easier.
Except that disabling it (with 0) reportedly did not solve the problem. There is
a possibility that its a more complex issue...
Ed Tomlinson
next prev parent reply other threads:[~2004-12-20 12:07 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 6:51 2.6.10-rc3: kswapd eats CPU on start of memory-eating task 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 [this message]
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
-- 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-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-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=200412200706.06534.edt@aei.ca \
--to=edt@aei.ca \
--cc=akpm@osdl.org \
--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.