From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Peter Staubach <staubach@redhat.com>
Cc: Kenny Simpson <theonetruekenny@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: another nfs puzzle
Date: Wed, 07 Dec 2005 11:09:40 -0500 [thread overview]
Message-ID: <1133971780.27373.64.camel@lade.trondhjem.org> (raw)
In-Reply-To: <4397063A.2030200@redhat.com>
On Wed, 2005-12-07 at 10:56 -0500, Peter Staubach wrote:
> I do know of other operating systems which do implement the semantics that I
> have suggested and I don't think that they are concerned or have been
> notified
> that these semantics for a problem. These semantics are used because the
> kernel itself can not even guarantee that the data that it is caching is
> valid,
> without lots of synchronization which may tend to reduce performance.
I agree. It is clearly going to be a drag on performance, but it should
be very much a corner case, so...
To tell you the truth, I'm more interested in this case in order to
figure out how to make mmap() work correctly for the case of an ordinary
file, but where the file changes on the server. Currently we just call
invalidate_inode_pages2(), without unmapping first. The conclusion from
Kenny's testcase appears to be that this may lead to mmapped dirty data
being lost.
Cheers,
Trond
next prev parent reply other threads:[~2005-12-07 16:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 22:04 Kenny Simpson
2005-12-07 3:24 ` Trond Myklebust
2005-12-07 14:50 ` Kenny Simpson
2005-12-07 14:01 ` Peter Staubach
2005-12-07 14:11 ` Trond Myklebust
2005-12-07 14:18 ` Peter Staubach
2005-12-07 14:34 ` Trond Myklebust
2005-12-07 15:34 ` Peter Staubach
2005-12-07 15:41 ` Trond Myklebust
2005-12-07 15:56 ` Peter Staubach
2005-12-07 16:09 ` Trond Myklebust [this message]
2005-12-07 16:39 ` Peter Staubach
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=1133971780.27373.64.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=staubach@redhat.com \
--cc=theonetruekenny@yahoo.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
all inboxes | Powered by JetHome®