And thanx for your reply.
> > And then there are slow files and slow directories. Reading block from
> > slow file can take something like 30 minutes in worst case. Reading
> > slow directory will be faster, but it can well take 2 minutes or so.
>
> NFSv3 would help you with this; it is supposed to return NFS3ERR_JUKEBOX
> in this case (and then you need a client that can grok this error).
I assume that linux nfs client is not good in this regard. (Is it?)
> > Question 2 is: what should nfs server do while trying to read block?
> > My current version just drops the request...
(As I understand it from NFSv3 spec, I should return NFS3ERR_JUKEBOX,
as you suggest above.)
> This service should most likely be used over a TCP connection only.
> In this case, you can hook a procedure into the TCP SVCXPRT receive
> routine that forks whenever a TCP connection comes in (you'll need
> a recent unfsd for this that does work multi-threaded).
Do recent unfsd-s support multithreaded servers read/write?
Pavel
-- The best software in life is free (not shareware)! Pavel GCM d? s-: !g p?:+ au- a--@ w+ v- C++@ UL+++ L++ N++ E++ W--- M- Y- R+- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu