From: "Raghu R. Arur" <rra2002@aria.ncl.cs.columbia.edu>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Eugene Teo <eugene.teo@eugeneteo.net>, linux-mm@kvack.org
Subject: Re: Understanding page faults code in mm/memory.c
Date: Thu, 31 Jul 2003 12:12:08 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.51.0307311209220.8932@aria.ncl.cs.columbia.edu> (raw)
In-Reply-To: <Pine.LNX.4.53.0307311242370.10913@skynet>
>
> > [3] in mm/memory.c, in do_wp_page, I am not sure what the
> > portion of code is about:
> >
> > // If old_page bit is not set, set it, and test.
> > if (!TryLockPage(old_page) {
> >
> > // [QN:] I don't understand what can_share_swap_page() do
> > // I tried tracing, but i still don't quite get it.
> > int reuse = can_share_swap_page(old_page);
>
> Basically it'll determine if you are the only user of that swap page. If
> it returns true, it means that you are the last process to break COW on
> that page so just use it. Otherwise it'll fall through and a new page will
> be allocated.
But when you put a page on to the swap cache will not the rss of the
address spage decrease. if not then when will the rss value of the
address space change.
thanks,
Raghu
--
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/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-07-31 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 11:15 Eugene Teo
2003-07-31 11:47 ` Mel Gorman
2003-07-31 16:12 ` Raghu R. Arur [this message]
2003-07-31 17:06 ` Mel Gorman
2003-07-31 17:11 ` Raghu R. Arur
2003-07-31 18:20 ` Mel Gorman
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=Pine.GSO.4.51.0307311209220.8932@aria.ncl.cs.columbia.edu \
--to=rra2002@aria.ncl.cs.columbia.edu \
--cc=eugene.teo@eugeneteo.net \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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