On Thu, Sep 19, 2013 at 08:49:47PM +0530, Prateek Lokur wrote:
1. Please give me the architecture diagram of netBSD OS(OS
schematic diagram).
The internals are documented here:
http://www.netbsd.org/docs/internals/en/
2. Brief on the performance on the NetBSD OS.
I'm sorry but that is a
Emmanuel Dreyfus m...@netbsd.org wrote:
I tried moving a client NFS mount to async. The result is that the
server never sees a filesync again from that client.
Further testing shows that server with -o log / client with -o async has
no performance problem. OTOH, the client sometimes
Thor Lancelot Simon t...@panix.com wrote:
It should be possible to gather those requests and commit many of them
at once to disk with a single cache flush operation, rather than issuing
a cache flush for each one. This is not unlike the problem with nfs3 in
general, that many clients at once
I tried moving a client NFS mount to async. The result is that the
server never sees a filesync again from that client.
Further testing shows that server with -o log / client with -o async has
no performance problem. OTOH, the client sometimes complain about write
errors. -o async
I tried moving a client NFS mount to async. [...]
Further testing shows that server with -o log / client with -o async
has no performance problem. OTOH, the client sometimes complain
about write errors. -o async seems dangerous.
-o async is very dangerous. there's not even the vaguest
