From: Andrew Morton <andrewm@uow.edu.au>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: vmtruncate question
Date: Fri, 14 Jul 2000 22:57:01 +1000 [thread overview]
Message-ID: <396F0E1D.AE1C4D27@uow.edu.au> (raw)
In-Reply-To: <20000714111802.R3113@redhat.com>
"Stephen C. Tweedie" wrote:
>
> Hi,
>
> On Wed, Jul 12, 2000 at 01:53:44AM +0000, Andrew Morton wrote:
> > The flushes which surround the second call to zap_page_range()
> > would appear to be flushing more memory than is to be
> > zapped. Is this correct, or should it be:
>
> Yes, I noticed that too: I think you're right.
OK, thanks. I'll implement this in the changes which are part of the
low-lat patch and send it off to LT tonight. If he says "no
low-latency" then I'll make sure this issue isn't forgotten about.
--
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/
prev parent reply other threads:[~2000-07-14 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-12 1:53 Andrew Morton
2000-07-14 10:18 ` Stephen C. Tweedie
2000-07-14 12:57 ` Andrew Morton [this message]
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=396F0E1D.AE1C4D27@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox