From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Benjamin C.R. LaHaise" <blah@kvack.org>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
"Eric W. Biederman" <ebiederm+eric@ccr.net>,
linux-mm@kvack.org
Subject: Re: [PATCH] dirty pages in memory & co.
Date: Tue, 11 May 1999 00:43:48 +0100 (BST) [thread overview]
Message-ID: <14135.28468.394799.280791@dukat.scot.redhat.com> (raw)
In-Reply-To: <Pine.LNX.3.95.990510164506.10344A-100000@as200.spellcast.com>
Hi,
On Mon, 10 May 1999 17:01:50 -0400 (EDT), "Benjamin C.R. LaHaise"
<blah@kvack.org> said:
> Hmmm, it shouldn't be a problem if the write blocks the reading of the
> page and PG_uptodate isn't set. This conflicts with the current
> assumption in generic_file_read that a locked page becoming unlocked
> without PG_uptodate being set indicates an error -- the best thing here
> is probably to add a PG_error flag and do away with the overloading.
I'm not convinced: doing an explicit read-page and waking up to find it
not uptodate sure sounds like an error to me. If we find a page which
isn't uptodate, then the first thing we do is try to read it, we don't
generate the error immediately. Why do we need a new flag?
--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-05-10 23:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-07 14:56 Eric W. Biederman
1999-05-10 0:57 ` Andrea Arcangeli
1999-05-11 1:06 ` Eric W. Biederman
1999-05-11 11:38 ` Andrea Arcangeli
1999-05-11 18:45 ` Stephen C. Tweedie
1999-05-10 19:37 ` Stephen C. Tweedie
1999-05-10 21:01 ` Benjamin C.R. LaHaise
1999-05-10 23:43 ` Stephen C. Tweedie [this message]
1999-05-11 0:30 ` Eric W. Biederman
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=14135.28468.394799.280791@dukat.scot.redhat.com \
--to=sct@redhat.com \
--cc=blah@kvack.org \
--cc=ebiederm+eric@ccr.net \
--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