From owner-freebsd-hackers Sun Feb 20 10:58:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 87FE237BEF4 for ; Sun, 20 Feb 2000 10:58:22 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (sol.cs.binghamton.edu [128.226.123.100]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id NAA11046 for ; Sun, 20 Feb 2000 13:58:14 -0500 (EST) Date: Sun, 20 Feb 2000 12:37:06 -0500 (EST) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: Two questions on NFS source code Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have spent some time understanding the NQNFS code and have two questions to ask: (1) People say we can not do write-behind on the NFS server side. Does this mean all vnode I/O must be performed with IO_SYNC (or other similar) flag set on the server side when the I/O is done on behalf of a NFS client? (2) NQNFS uses the concept of write slack time. What will happen if a NFS client fails to write the modified buffer back to the server's stable storage within that slack time? Will the late write request be discarded by the server? Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message