Date: Tue, 4 Apr 2000 16:59:00 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Alfred Perlstein <bright@wintelcom.net> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: reducing the number of NFSv3 commit ops Message-ID: <14570.22237.61025.935384@grasshopper.cs.duke.edu> In-Reply-To: <20000404141641.P20770@fw.wintelcom.net> References: <14570.10864.359054.10598@grasshopper.cs.duke.edu> <20000404141641.P20770@fw.wintelcom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Alfred Perlstein writes: > > > > Can anybody tell me if doing something like this is fundamentally > > broken? Is it worth pursuing? > > http://www.freebsd.org/~alfred/nfs_supercommit_broken.diff > > only grab as many adjacent blocks as possible, you don't want to > scan the entire file's buffer list for each commit, you also don't > want to interfere with other client's caching forcing sever commits > on thier behalf. > I'll look at that tonight. But before I do -- why is it broken? (the name sorta implies that it us ;) Thanks! Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14570.22237.61025.935384>