[src/netbsd-1-5]: src/sys/ufs/lfs Pull up revision 1.45 (requested by fvdl):

[he <he%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/777aa4c808bc
branches:  netbsd-1-5
changeset: 490329:777aa4c808bc
user:      he <he%NetBSD.org@localhost>
date:      Thu Dec 14 23:36:31 2000 +0000

description:
Pull up revision 1.45 (requested by fvdl):
  Improve NFS performance, possibly with as much as 100% in
  throughput.  Please note: this implies a kernel interface change,
  VOP_FSYNC gains two arguments.

diffstat:

 sys/ufs/lfs/lfs_vnops.c |  6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

diffs (27 lines):

diff -r e3210c5898bd -r 777aa4c808bc sys/ufs/lfs/lfs_vnops.c
--- a/sys/ufs/lfs/lfs_vnops.c   Thu Dec 14 23:36:29 2000 +0000
+++ b/sys/ufs/lfs/lfs_vnops.c   Thu Dec 14 23:36:31 2000 +0000
@@ -1,4 +1,4 @@
-/*     $NetBSD: lfs_vnops.c,v 1.38.2.4 2000/11/01 16:34:31 tv Exp $    */
+/*     $NetBSD: lfs_vnops.c,v 1.38.2.5 2000/12/14 23:36:31 he Exp $    */
 
 /*-
  * Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
@@ -284,6 +284,8 @@
                struct vnode *a_vp;
                struct ucred *a_cred;
                int a_flags;
+               off_t offlo;
+               off_t offhi;
                struct proc *a_p;
        } */ *ap = v;
        
@@ -494,7 +496,7 @@
         * return.  But, that leaves this vnode in limbo, also not good.
         * Can this ever happen (barring hardware failure)?
         */
-       if ((error = VOP_FSYNC(*vpp, NOCRED, FSYNC_WAIT, curproc)) != 0) {
+       if ((error = VOP_FSYNC(*vpp, NOCRED, FSYNC_WAIT, 0, 0, curproc)) != 0) {
                printf("Couldn't fsync in mknod (ino %d)---what do I do?\n",
                       VTOI(*vpp)->i_number);
                return (error);