linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andrea Arcangeli <andrea@suse.de>
Cc: "Juan J. Quintela" <quintela@fi.udc.es>,
	linux-mm@kvack.org, linux-kernel@vger.rutgers.edu
Subject: Re: classzone-VM + mapped pages out of lru_cache
Date: Thu, 4 May 2000 21:32:21 +0200 (CEST)	[thread overview]
Message-ID: <14609.53317.581465.821028@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.21.0005042022200.3416-100000@alpha.random>

>>>>> " " == Andrea Arcangeli <andrea@suse.de> writes:

     > On 4 May 2000, Trond Myklebust wrote:
    >> Not good. If I'm running /bin/bash, and somebody on the server
    >> updates /bin/bash, then I don't want to reboot my machine. With
    >> the above

     > If you use rename(2) to update the shell (as you should since
     > `cp` would corrupt also users that are reading /bin/bash from
     > local fs) then nfs should get it right also with my patch since
     > it should notice the inode number changed (the nfs fd handle
     > should get the inode number as cookie), right?

Yes, but I'm on the client: I cannot guarantee that people on the
server will do it 'right'. The server can have temporarily dropped
down into single user mode in order to protect its own users for all I
know.

Accuracy has to be the first rule whatever the case.

     > The only problem I am wondering about is that we simply can't
     > unlink _mapped_ page-cache pages from the pagecache as we do
     > now.

     > Say there's page A in the page cache. It gets mapped into a pte
     > of process
     > X. Then before you can drop A from the page cache to invalidate
     >    it
     > (because such page changed on the nfs server), you _first_ have
     > to unmap such page from the pte of process X. This is why
     > invalidate_inode_pages must not unlink mapped pages. It's not a
     > locking problem, PageLocked() pagecache_lock and all other
     > locks are irrelevant. It's not a race but a design issue.

As far as NFS is concerned, that page is incorrect and should be read
in again whenever we next try to access it. That is the purpose of the
call to invalidate_inode_pages().  As far as I can see, your patch
fundamentally breaks that concept for all files whether they are
mmapped or not.

When you say 'unmap from the pte', what exactly do you mean? Why does
such a page still have to be part of an inode's i_data?

Cheers,
  Trond
--
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/

  reply	other threads:[~2000-05-04 19:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-03 16:26 Andrea Arcangeli
2000-05-04  0:42 ` David S. Miller
2000-05-04 10:00   ` Andrea Arcangeli
2000-05-04 14:40 ` Juan J. Quintela
2000-05-04 15:19   ` Andrea Arcangeli
2000-05-04 15:23     ` Andrea Arcangeli
2000-05-04 15:38     ` Rik van Riel
2000-05-04 17:59       ` Andrea Arcangeli
2000-05-04 19:24         ` Rik van Riel
2000-05-04 16:34     ` Manfred Spraul, Andrea Arcangeli
2000-05-04 16:48     ` Trond Myklebust
2000-05-04 18:43       ` Andrea Arcangeli
2000-05-04 19:32         ` Trond Myklebust [this message]
2000-05-04 20:15           ` Andrea Arcangeli
2000-05-05  7:01             ` Trond Myklebust
2000-05-04 16:34   ` Juan J. Quintela
2000-05-04 18:27     ` Chris Evans
     [not found] <3911ECCD.BA1BB24E@arcormail.de>
2000-05-04 23:44 ` Andrea Arcangeli
2000-05-05  0:03   ` Jens Axboe
2000-05-05  3:04   ` David S. Miller
2000-05-05  8:43     ` Russell King
2000-05-05 14:56     ` Andrea Arcangeli
2000-05-06 13:37   ` Andrea Arcangeli

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=14609.53317.581465.821028@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=quintela@fi.udc.es \
    /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