NFSv4.1 Server DRC rewrite Version 4 This patch set applies to linux-nfs.org/~bfields/linux, for-2.6.31 branch updated on 6-22-2009. In response to bfield's comments I moved the DRC limit bug fixes to the front of the series, consolidated patches replacing the single slot clientid DRC into one patch and the replacement of the mulitple slot sequeqnce operation DRC into another single patch. The NFSv4.1 DRC is changed from a page based cache to a buffer based cache. The logic for the single slot clientid cache has been separated from the session slot logic to handle the CREATE_SESSION call preceeded by a SEQUENCE and all the replay combinations therein. The session DRC now caches encoded operations with the exception of the SEQUENCE operation which for a replay is encoded with the current slot and session values. A review of message sizes indicates that a 512 byte buffer for the operations is adequate. Not addressed is replacing the nfsd4_check_drc_limit() post-operation checking with a pre-operation processing estimate of the encoded per operation result Testing: 4.1 mount: Connectathon and 4.1pynfs including the new create session replay tests. 4.0 mount; Connectathon. 0001-nfsd41-use-globals-for-DRC-limits.patch 0002-nfsd41-change-from-page-to-memory-based-drc-limits.patch 0003-nfsd41-reclaim-DRC-memory-on-session-free.patch 0004-nfsd41-set-the-session-maximum-response-size-cached.patch 0005-nfsd41-remove-redundant-forechannel-max-requests-ch.patch 0006-nfsd41-change-check_slot_seqid-parameters.patch 0007-nfsd41-replace-create_session-DRC-with-xdr-structur.patch 0008-nfsd41-replace-page-based-DRC-with-buffer-based-DRC.patch 0009-nfsd41-rename-nfsd4_enc_uncached_replay.patch 0010-nfsd41-encode-replay-sequence-from-the-slot-values.patch 0011-nfsd41-fix-nfsd4_replay_cache_entry-comments.patch 0012-nfsd41-support-16-slots-per-session.patch 0013-nfsd41-add-test-for-failed-sequence-operation.patch 0014-nfsd41-remove-redundant-failed-sequence-check.patch Comments welcome. -->Andy -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
