linux-toradex.git/include/linux/nfs_xdr.h, branch v3.8.12

NFSv4.1: Move the RPC timestamp out of the slot.

2012-12-15T20:21:52+00:00

Shave a few bytes off the slot table size by moving the RPC timestamp
into the sequence results.

Signed-off-by: Trond Myklebust

NFSv4: Reorder the XDR structures to put sequence at the top, not bottom

2012-12-05T23:30:52+00:00

Pre-condition for optimising the slot allocation and reintroducing FIFO
behaviour.

Signed-off-by: Trond Myklebust

NFSv4: Clean up handling of privileged operations

2012-12-05T23:30:50+00:00

Privileged rpc calls are those that are run by the state recovery thread,
in cases where we're trying to recover the system after a server reboot
or a network partition. In those cases, we want to fence off all other
rpc calls (see nfs4_begin_drain_session()) so that they don't end up
using stateids or clientids that are in the process of being recovered.

Prior to this patch, we had to set up special callback functions in
order to declare an rpc call as being privileged.
By adding a new field to the sequence arguments, this patch simplifies
things considerably, and allows us to declare the rpc call as privileged
before it is run.

Signed-off-by: Trond Myklebust

NFSv4.1: Move slot table and session struct definitions to nfs4session.h

2012-12-05T23:30:46+00:00

Clean up. Gather NFSv4.1 slot definitions in fs/nfs/nfs4session.h.

Signed-off-by: Trond Myklebust

NFSv4.1: Allow SEQUENCE to resize the slot table on the fly

2012-12-05T23:30:42+00:00

Instead of an array of slots, use a singly linked list of slots that
can be dynamically appended to or shrunk.

Signed-off-by: Trond Myklebust

NFSv4.1: Reset the sequence number for slots that have been deallocated

2012-12-05T23:30:17+00:00

When the server tells us that it is dynamically resizing the session
replay cache, we should reset the sequence number for those slots
that have been deallocated.

Signed-off-by: Trond Myklebust

NFSv4.1: Ensure that the client tracks the server target_highest_slotid

2012-12-05T23:29:47+00:00

Dynamic slot allocation in NFSv4.1 depends on the client being able to
track the server's target value for the highest slotid in the
slot table.  See the reference in Section 2.10.6.1 of RFC5661.

To avoid ordering problems in the case where 2 SEQUENCE replies contain
conflicting updates to this target value, we also introduce a generation
counter, to track whether or not an RPC containing a SEQUENCE operation
was launched before or after the last update.

Also rename the nfs4_slot_table target_max_slots field to
'target_highest_slotid' to avoid confusion with a slot
table size or number of slots.

Signed-off-by: Trond Myklebust

NFSv4.1: Simplify struct nfs4_sequence_args too

2012-11-26T22:49:52+00:00

Replace the session pointer + slotid with a pointer to the
allocated slot.

Signed-off-by: Trond Myklebust

NFSv4.1: Label each entry in the session slot tables with its slot number

2012-11-26T22:49:51+00:00

Instead of doing slot table pointer gymnastics every time we want to
know which slot we're using.

Signed-off-by: Trond Myklebust

NFSv4.1: Shrink struct nfs4_sequence_res by moving the session pointer

2012-11-26T22:49:04+00:00

Move the session pointer into the slot table, then have struct nfs4_slot
point to that slot table.

Signed-off-by: Trond Myklebust