From: Rajagopal Ananthanarayanan <ananth@sgi.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-mm@kvack.org
Subject: Re: Odd swap behavior
Date: Wed, 04 Oct 2000 15:05:30 -0700 [thread overview]
Message-ID: <39DBA9AA.AA4DEB1C@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0010041844510.1054-100000@duckman.distro.conectiva>
Rik van Riel wrote:
[ ... ]
>
> Please take a look at vmscan.c::refill_inactive()
>
> Furthermore, we don't do background scanning on all
> active pages, only on the unmapped ones.
Does that mean stack pages of processes are not included?
Non-aggressive swap can hurt performance.
>
> Agreed, but I don't see an "easy" solution for 2.4.
>
Ok, I have another suggestion. Suppose you had a situation
where a page is read from disk. It has buffers. Initially
the page is active, and then aged. Where does the page go at age = 0?
In reading the current code it seems that it would go to
inactive_dirty. See how deactivate_page() chooses the dirty list
to add a page which has buffers. Of course, later page_launder()
would do try_to_free_buffers() which discards (clean) buffer heads,
and at that point the page is put on free_list/reclaimed.
Would it not be more efficient to bung clean (read) pages directly
to inactive_clean on age = 0?
--------------------------------------------------------------------------
Rajagopal Ananthanarayanan ("ananth")
Member Technical Staff, SGI.
--------------------------------------------------------------------------
--
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:[~2000-10-04 22:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-04 0:23 Rajagopal Ananthanarayanan
2000-10-04 15:14 ` Rik van Riel
2000-10-04 21:39 ` Rajagopal Ananthanarayanan
2000-10-04 21:46 ` Rik van Riel
2000-10-04 22:05 ` Rajagopal Ananthanarayanan [this message]
2000-10-04 22:13 ` Rik van Riel
2000-10-04 23:03 ` Rajagopal Ananthanarayanan
2000-10-05 0:07 ` Rik van Riel
2000-10-05 2:31 ` Rajagopal Ananthanarayanan
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=39DBA9AA.AA4DEB1C@sgi.com \
--to=ananth@sgi.com \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
/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