From: ebiederm@xmission.com (Eric W. Biederman)
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-mm@kvack.org
Subject: Consistent page aging....
Date: 25 Jul 2001 04:10:48 -0600 [thread overview]
Message-ID: <m1n15tgvyv.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0107250416230.2823-100000@freak.distro.conectiva>
Marcelo Tosatti <marcelo@conectiva.com.br> writes:
> Sorry, Eric.
>
> The biggest 2.4 swapping bug is that we need to allocate swap space for a
> page to be able to age it.
Well I guess biggest bug is a debatable title.
> We had to be able to age pages without allocating swap space...
That sounds reasonable. I haven't been over the aging code lately it
keeps changing. You say this hasn't been fixed? Looking... O.k. I
see what you are talking about.
I don't see any technical reasons why we can't do this. Doing it
without adding many extra special cases would require some thinking
but nothing fundamental says you can't have anonymous pages in the
active list. You can't move mapped pages off of the active list
but this holds true anyway.
The only benefit this would bring is that after anonymous pages have
been converted to swappable pages they wouldn't start at the end of
the active_list.
I can see how this would be helpful, but unless you benchmark this
I don't see how this can as the biggest 2.4 swapping bug.
Eric
--
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-mm.org/
next parent reply other threads:[~2001-07-25 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0107250416230.2823-100000@freak.distro.conectiva>
2001-07-25 10:10 ` Eric W. Biederman [this message]
2001-07-25 10:11 ` Marcelo Tosatti
2001-07-25 15:49 ` Rik van Riel
2001-07-25 16:08 ` Eric W. Biederman
2001-07-25 16:42 ` Rik van Riel
2001-07-26 7:19 ` Eric W. Biederman
2001-07-25 16:02 ` Eric W. Biederman
2001-07-26 10:04 ` Marcelo Tosatti
2001-07-26 14:46 ` Eric W. Biederman
2001-07-27 23:45 ` Jordi Polo
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=m1n15tgvyv.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=linux-mm@kvack.org \
--cc=marcelo@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