[pnfs] Server sessions slot table patches

[William A. (Andy) Adamson]

On 4/3/07, Iyer, Rahul <Rahul.Iyer at netapp.com> wrote:
>
> The reason the client uses slot 0 is because most of the ops are
> serialized, and connectathon is single threaded. The part where it goes
> to using slots > 1 is on writes because these can happen in parallel.



actually,  the slot 1 compounds were

mostly
PUTFH
GETATTR

but these are probably retries - they were all for the same filehandle

one
PUTFH
SETATTR
GETATTR

all the WRITES were on slot 0


-->Andy

As for whether it's the client or the server, it should be fairly simple
> to find out. I can do that once (a reviewed form of) these patches gets
> into the tree.

Regards
> Rahul
>
>
> > -----Original Message-----
> > From: William A. (Andy) Adamson [mailto:andros at citi.umich.edu]
> > Sent: Tuesday, April 03, 2007 6:43 AM
> > To: pnfs at linux-nfs.org
> > Subject: [pnfs] Server sessions slot table patches
> >
> > hi
> >
> > here are 9 patches that implement the server slot table
> > management. there is not DRC yet, but this code has been
> > developed with the DRC in mind. This code almost passes the
> > connectathon tests on the 4.1-sessions branch with the client
> > patches i just sent out.
> >
> > it fails the general connectathon tests with an
> > NFS4ERR_SEQ_MISORDERED. i note that the client mostly uses
> > slot 0, and occasionally uses slot 1. the slot 1 sequence is
> > out of order - i don't know if it is the client or server.
> >
> > please review the patches...
> >
> > thanks
> >
> > -->Andy
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://linux-nfs.org/pipermail/pnfs/attachments/20070403/a664c293/attachment.htm