From: ebiederm+eric@ccr.net (Eric W. Biederman)
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] dirty pages in memory & co.
Date: 10 May 1999 19:30:00 -0500 [thread overview]
Message-ID: <m1hfpke9dj.fsf@flinx.ccr.net> (raw)
In-Reply-To: "Stephen C. Tweedie"'s message of "Mon, 10 May 1999 20:37:38 +0100 (BST)"
>>>>> "ST" == Stephen C Tweedie <sct@redhat.com> writes:
ST> Hi,
ST> On 07 May 1999 09:56:00 -0500, ebiederm+eric@ccr.net (Eric W. Biederman)
ST> said:
>> It looks like I need 2 variations on generic_file_write at the
>> moment.
>> 1) for network filesystems that can get away without filling
>> the page on a partial write.
>> 2) for block based filesystems that must fill the page on a
>> partial write because they can't write arbitrary chunks of
>> data.
ST> I'd be very worried by (1): sounds like a partial write followed by a
ST> read of the full page could show up garbage in the page cache if you do
ST> this. If NFS skips the page clearing for partial writes, how does it
ST> avoid returning garbage later?
Actually (1) is current behaviour. I really don't like it but I can see
how it can potentially improve performance. Partial writes are handled
by not setting PG_uptodate.
Reads are handled by always flushing the per page dirty data before reading.
I don't especially like it but it's what we have now.
Eric
--
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/
prev parent reply other threads:[~1999-05-11 2:42 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
1999-05-11 0:30 ` Eric W. Biederman [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=m1hfpke9dj.fsf@flinx.ccr.net \
--to=ebiederm+eric@ccr.net \
--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