From: Christoph Rohland <hans-christoph.rohland@sap.com>
To: Chuck Lever <cel@monkey.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
James Manning <jmm@computer.org>,
linux-mm@kvack.org
Subject: Re: a plea for mincore()/madvise()
Date: 11 Mar 2000 15:14:44 +0100 [thread overview]
Message-ID: <qwwd7p1ioff.fsf@sap.com> (raw)
In-Reply-To: Chuck Lever's message of "Fri, 10 Mar 2000 19:39:03 -0500 (EST)"
Chuck Lever <cel@monkey.org> writes:
> > I'd like MADV_DONTNEED to just clear the page tables. If it was a private
> > mapping, all the modifications get lost. If it was a shared mapping,
> > modifications since the last msync() may or may not get lost.
>
> i'll create a patch against 2.3.51-pre3 for madvise() and post it on the
> mm list before sunday. then we can argue about something we've both seen
> :)
>
> let me think some more about DONTNEED. at the face of it, i agree with
> your suggestion, but i may just exclude it from the patch until there is
> more discussion here.
As stated before I would be very interested in a call (perhaps
MADV_DONTNEED) which throws away shared (anon) memory pages.
Greetings
Christoph
--
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-03-11 14:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000310152650.A14388@nina.pagesz.net>
2000-03-10 21:13 ` a plea for mincore()/madvise() Linus Torvalds
2000-03-10 21:36 ` Chuck Lever
2000-03-10 21:46 ` Linus Torvalds
2000-03-10 23:41 ` Chuck Lever
2000-03-11 0:14 ` Linus Torvalds
2000-03-11 0:39 ` Chuck Lever
2000-03-11 14:14 ` Christoph Rohland [this message]
2000-03-13 8:43 ` Richard Guenther
2000-03-13 16:03 ` Stephen C. Tweedie
2000-03-13 17:20 ` Chuck Lever
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=qwwd7p1ioff.fsf@sap.com \
--to=hans-christoph.rohland@sap.com \
--cc=cel@monkey.org \
--cc=jmm@computer.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@transmeta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.