linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kanoj@google.engr.sgi.com (Kanoj Sarcar)
To: riel@nl.linux.org
Cc: Russell King <rmk@arm.linux.org.uk>,
	linux-mm@kvack.org, linux-kernel@vger.rutgers.edu,
	torvalds@transmeta.com
Subject: Re: [PATCH] Re: kswapd
Date: Sun, 26 Mar 2000 18:39:14 -0800 (PST)	[thread overview]
Message-ID: <200003270239.SAA97539@google.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0003262327160.1104-100000@duckman.conectiva> from "Rik van Riel" at Mar 26, 2000 11:28:30 PM

> 
> On Sun, 26 Mar 2000, Kanoj Sarcar wrote:
> > > On Sun, 26 Mar 2000, Russell King wrote:
> > > 
> > > > I think I've solved (very dirtily) my kswapd problem
> > > 
> > > Your patch is the correct one. I've added an extra reschedule
> > > point and cleaned up the code a little bit. I wonder who sent
> > > the brown-paper-bag patch with the superfluous while loop to
> > > Linus ...        (please raise your hand and/or buy rmk a beer)
> > 
> > That would be me ...
> > 
> > What is the problem that your patch is fixing?
> 
> Removing the superfluous while loop.
> 

Maybe I am being stupid, but where is the superfluous loop? Remember,
as I just pointed out, 2.3.43 had the same loop, are you claiming it 
was buggy even then?

> Without my patch kswapd uses between 50 and 70% CPU time
> in a particular workload. Now it uses between 3 and 5%.

Can you explain how this is happening? I can see that in your patch,
kswapd does not go thru the loop if need_resched is set, but with
a single node, 3 zones, I would find it hard to explain such a 
difference.

> Oh, and the latency problem probably has been fixed too...

What latency problem? I still believe that the pre3 code is doing
the right thing, assuming 2.3.43 was doing the right thing.

Kanoj

> 
> cheers,
> 
> Rik
> --
> The Internet is not a network of computers. It is a network
> of people. That is its real strength.
> 
> Wanna talk about the kernel?  irc.openprojects.net / #kernelnewbies
> http://www.conectiva.com/		http://www.surriel.com/
> 

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  reply	other threads:[~2000-03-27  2:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200003261008.LAA16031@raistlin.arm.linux.org.uk>
2000-03-27  0:59 ` Rik van Riel
2000-03-27  1:21   ` Kanoj Sarcar
2000-03-27  2:28     ` Rik van Riel
2000-03-27  2:39       ` Kanoj Sarcar [this message]
2000-03-27  6:42         ` Russell King
2000-03-27  6:02     ` Eric W. Biederman
2000-03-27  6:07     ` Linus Torvalds
2000-03-27  8:00       ` Kanoj Sarcar
2000-03-27 14:47         ` Rik van Riel
2000-03-27 16:14         ` Linus Torvalds
2000-03-27 16:54           ` Mark Hahn
2000-03-27 17:36             ` Linus Torvalds
2000-03-27 17:54             ` Rik van Riel
2000-03-27 18:55           ` Kanoj Sarcar
2000-03-27 18:34         ` Russell King

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=200003270239.SAA97539@google.engr.sgi.com \
    --to=kanoj@google.engr.sgi.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=riel@nl.linux.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox