Date: Sun, 22 Aug 1999 10:00:19 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Doug Rabson <dfr@nlsystems.com> Cc: "Matthew D. Fuller" <fullermd@futuresouth.com>, Steve Ames <steve@cioe.com>, freebsd-hackers@freebsd.org Subject: Re: Async NFS exports? Message-ID: <199908221700.KAA77935@apollo.backplane.com> References: <Pine.BSF.4.10.9908221735330.72739-100000@salmon.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
:> buffer cache is able to keep abrest of the write-rate. :> :> Hmm, interesting. I see another optimization I can do to fix the :> buffer cache saturation case in CURRENT on the client. The COMMIT rpc's :> aren't being issued async. : :You need to track the return value of the commit so that you can detect :server reboots and sync-write the data again. If you change to async, make :sure that you still keep this part - its essential to the protocol. : :-- :Doug Rabson Mail: dfr@nlsystems.com :Nonlinear Systems Ltd. Phone: +44 181 442 9037 These are buffer-cache entities we are talking about here, so they won't go away until NFS tells the system they can go away. In that respect async I/O is no different then sync I/O. async I/O is simply run synchronously from an nfsiod context. -Matt Matthew Dillon <dillon@backplane.com> 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?199908221700.KAA77935>