From: Linus Torvalds <torvalds@transmeta.com>
To: Chuck Lever <cel@monkey.org>
Cc: James Manning <jmm@computer.org>, linux-mm@kvack.org
Subject: Re: a plea for mincore()/madvise()
Date: Fri, 10 Mar 2000 16:14:10 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.10.10003101612470.906-100000@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.BSO.4.10.10003101825170.10894-100000@funky.monkey.org>
On Fri, 10 Mar 2000, Chuck Lever wrote:
>
> ja, that's exactly what my patch does. i'm still not sure what you don't
> like about it. i'm happy to make it do anything you want, but it sounds
> like we are in agreement here.
Ok. I may not have seen (or noticed) your patch, I've seen earlier patches
that didn't do that.
> my only sticking point is that i'm not sure what community consensus there
> is about MADV_DONTNEED. i'd like to create a patch that implements
> everything except MADV_DONTNEED, then maybe we should have more discussion
> about exactly how that will work and add it later.
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.
Linus
--
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 0: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 ` 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 [this message]
2000-03-11 0:39 ` Chuck Lever
2000-03-11 14:14 ` Christoph Rohland
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=Pine.LNX.4.10.10003101612470.906-100000@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=cel@monkey.org \
--cc=jmm@computer.org \
--cc=linux-mm@kvack.org \
/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