From: Zlatko Calusic <zlatko@iskon.hr>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Ed Tomlinson <tomlins@cam.org>, linux-mm@kvack.org
Subject: Re: pre2 swap_out() changes
Date: 14 Jan 2001 18:22:57 +0100 [thread overview]
Message-ID: <87bstahwum.fsf@atlas.iskon.hr> (raw)
In-Reply-To: Zlatko Calusic's message of "14 Jan 2001 17:15:39 +0100"
Zlatko Calusic <zlatko@iskon.hr> writes:
> Marcelo Tosatti <marcelo@conectiva.com.br> writes:
>
> > On Sun, 14 Jan 2001, Ed Tomlinson wrote:
> >
> > > Hi,
> > >
> > > A couple of observations on the pre2/pre3 vm. It seems to start swapping out
> > > very quicky but this does not seem to hurt. Once there is memory preasure
> > > and swapin starts cpu utilization drops thru the roof - kernel compiles are
> > > only able to drive the system at 10-20% (UP instead of 95-100%). Once the
> > > system stops swapping (in) there are some side effects. Closing windows
> > > in X becomes jerky (ie you see blocks get cleared and refreshed). If little
> > > or no swapping has occured X is much faster.
> > >
> > > With the patch marcelo posted last night things change. Now It can use cpu
> > > when swapping. It does seem to start swaping (in and out) faster but the
> > > system remains more interactive than above. I still see the X effect though.
> > >
> > > Over all I think 2.4.0+marcelo's first patch(es) was fastest.
> >
>
> My opinion exactly, Ed! Don't let me copy/paste all of your comment as
> mine just beacuse your English is better. :)
>
> > There is still a critical thing to be fixed which is the swapout selection
> > path (which is probably what is causing your problem in X)
> >
>
> Yes, while swapout code in pre3 is much cleaner and nicer to see, but
> it has problems with deciding what to swap out, and streaming it all
> well. Glad we agree. Will check your new patch now, to see if it helps.
With your last patch applied:
Kernel compilation is back to normal, under 4 minutes! Very good!
Memory hogger's behaviour haven't changed at all, for that problem to
solve we will need some major changes in the swap_out() and functions
it calls, I'm afraid.
--
Zlatko
--
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/
next prev parent reply other threads:[~2001-01-14 17:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 10:38 Marcelo Tosatti
2001-01-11 18:49 ` Linus Torvalds
2001-01-12 11:35 ` Zlatko Calusic
2001-01-12 19:45 ` Linus Torvalds
2001-01-12 19:22 ` Marcelo Tosatti
2001-01-13 0:23 ` Linus Torvalds
2001-01-12 22:41 ` Marcelo Tosatti
2001-01-13 0:45 ` Linus Torvalds
2001-01-17 7:05 ` Rik van Riel
2001-01-18 11:54 ` Rik van Riel
2001-01-13 11:41 ` Zlatko Calusic
2001-01-17 7:08 ` Rik van Riel
2001-01-13 11:51 ` Zlatko Calusic
2001-01-14 2:39 ` Marcelo Tosatti
2001-01-14 4:36 ` Linus Torvalds
2001-01-14 3:50 ` Marcelo Tosatti
2001-01-14 15:51 ` Ed Tomlinson
2001-01-14 14:13 ` Marcelo Tosatti
2001-01-14 16:15 ` Zlatko Calusic
2001-01-14 17:22 ` Zlatko Calusic [this message]
2001-01-17 7:16 ` Rik van Riel
2001-01-17 7:15 ` Rik van Riel
2001-01-17 7:12 ` Rik van Riel
2001-01-11 20:52 Benjamin Redelings I
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=87bstahwum.fsf@atlas.iskon.hr \
--to=zlatko@iskon.hr \
--cc=linux-mm@kvack.org \
--cc=marcelo@conectiva.com.br \
--cc=tomlins@cam.org \
/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