From: "Emery Berger" <emery@cs.umass.edu>
To: Rik van Riel <riel@redhat.com>, Yi Feng <yifeng@cs.umass.edu>
Cc: Rohit Seth <rohit.seth@intel.com>,
linux-mm@kvack.org, Andrew Morton <akpm@osdl.org>,
Matthew Hertz <hertzm@canisius.edu>
Subject: RE: [patch] vmsig: notify user applications of virtual memory events via real-time signals
Date: Wed, 23 Nov 2005 08:33:18 -0500 [thread overview]
Message-ID: <B061F5ED2860D9439AE34EE5C141938C090CF0@zor.ads.cs.umass.edu> (raw)
> Would it be better for the application to completely vacate
> the page, so MADV_DONTNEED can be used instead, and swap IO
> can be avoided ?
Yes, but under severe memory pressure, it is not possible.
-- emery
--
Emery Berger
Assistant Professor
Dept. of Computer Science
University of Massachusetts, Amherst
www.cs.umass.edu/~emery
> -----Original Message-----
> From: Rik van Riel [mailto:riel@redhat.com]
> Sent: Wednesday, November 23, 2005 8:11 AM
> To: Yi Feng
> Cc: 'Rohit Seth'; Emery Berger; linux-mm@kvack.org; 'Andrew Morton';
> 'Matthew Hertz'
> Subject: RE: [patch] vmsig: notify user applications of virtual memory
> events via real-time signals
>
> On Wed, 23 Nov 2005, Yi Feng wrote:
>
> > When the application receives this notification and starts to
process
> this
> > page, this page will stay in core (possibly for a fairly long time)
> because
> > it's been touched again. That's why we also added
> madvise(MADV_RELINQUISH)
> > to explicitly send the page to swap after the processing.
>
> Would it be better for the application to completely vacate
> the page, so MADV_DONTNEED can be used instead, and swap IO
> can be avoided ?
>
> --
> All Rights Reversed
--
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:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2005-11-23 13:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 13:33 Emery Berger [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-22 21:53 Emery Berger
2005-11-23 2:29 ` Rohit Seth
2005-11-23 5:00 ` Yi Feng
2005-11-23 13:11 ` Rik van Riel
2005-11-23 16:30 ` Yi Feng
2005-11-22 20:54 Yi Feng
2005-11-22 21:45 ` Rik van Riel
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=B061F5ED2860D9439AE34EE5C141938C090CF0@zor.ads.cs.umass.edu \
--to=emery@cs.umass.edu \
--cc=akpm@osdl.org \
--cc=hertzm@canisius.edu \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=rohit.seth@intel.com \
--cc=yifeng@cs.umass.edu \
/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