public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Voluspa <lista4@comhem.se>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, nickpiggin@yahoo.com.au, mr@ramendik.ru,
	kernel@kolivas.org
Subject: Re: 2.6.10-rc3: kswapd eats CPU on start of memory-eating task
Date: Sun, 19 Dec 2004 23:40:59 +0100 (MET)	[thread overview]
Message-ID: <14514245.1103496059334.JavaMail.tomcat@pne-ps4-sn2> (raw)


Found the first kernel version with the regression. It's linux-2.6.9-rc1

Perusing lkml from august there was a short thread about the oopses and loss 
of keyboard in X. Applying that information in a crude hack I was able to 
test the effected 2.6.9-rc1 and three -bk forward:

http://marc.theaimsgroup.com/?t=109357291300002&r=1&w=2

diff -Naur linux-2.6.9-rc1/net/sunrpc/svcauth_unix.c linux-2.6.9-rc1-debug/net/sunrpc/svcauth_unix.c
--- linux-2.6.9-rc1/net/sunrpc/svcauth_unix.c   2004-12-15 18:39:28.000000000 
+0100
+++ linux-2.6.9-rc1-debug/net/sunrpc/svcauth_unix.c     2004-12-19 19:01:
53.000000000 +0100
@@ -104,7 +104,6 @@
                if (test_bit(CACHE_VALID, &item->flags) &&
                    !test_bit(CACHE_NEGATIVE, &item->flags))
                        auth_domain_put(&im->m_client->h);
-               kfree(im->m_class);
                kfree(im);
        }
 }

I've since tested and retested for several hours on the different kernels. At one 
point I thought the usage of lapic=lapic made a difference, but it turned 
out to be a red herring.

2.6.8.1-bk2 is without doubt the last kernel to handle my testcase "properly". There 
are no freezes whatsoever and the swapping is finished within 1 minute and 
some seconds.

2.6.9-rc1 and forward all have the freezes. Swapping and readback takes from 
3 to 6 minutes. I can't find a pattern in the time differences.

What's left now is to find some repository which has the gargantuan 2.6.9-rc1 
broken out in its pieces (and I guess 2.6.8.1-bk1 and 2 must be subtracted 
from that). Then reverting patches. A process where I'd need some handholding 
as to what would be likely candidates.

An innocent one is Ingo's "context-switching overhead in X, ioport()" patch. 
I added it to 2.6.8.1-bk2 and it didn't break my testcase.

Ah, well. It's that time of the year, so I won't be able to do any testing until 
the madness is over.

Mvh
Mats Johannesson


             reply	other threads:[~2004-12-19 22:41 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-19 22:40 Voluspa [this message]
2004-12-19 22:56 ` 2.6.10-rc3: kswapd eats CPU on start of memory-eating task 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
  -- 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=14514245.1103496059334.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