Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee

From: Alan Cox (alan@lxorguk.ukuu.org.uk)
Date: Sat Sep 16 2000 - 12:57:28 EST

Next message: octave klaba: "folk: no more resource available"
Previous message: Rik van Riel: "Re: Very aggressive swapping after 2 hours rest"
In reply to: Michael Eisler: "Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee"
Next in thread: Trond Myklebust: "Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> I'm not a Linux kernel literate. However, I found your
> assertion surprising. Does procfs do page i/o as well?

No. An fs isnt required to use the page caches at all. It makes life a lot saner
to do so

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Next message: octave klaba: "folk: no more resource available"
Previous message: Rik van Riel: "Re: Very aggressive swapping after 2 hours rest"
In reply to: Michael Eisler: "Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee"
Next in thread: Trond Myklebust: "Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 21:00:13 EST