Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 4975] NFSv4 usability enhancements (Info column summaries,

Date: Tue, 6 Jul 2010 07:49:07 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4975

--- Comment #8 from Ian Schorr <ian.schorr@xxxxxxxxx> 2010-07-06 07:49:05 PDT ---
Actually I originally had an artificial upper limit of 500 at one point, though
I don't remember now why it was removed (and clearly one should have been
re-added).

I don't see any specific maximum (besides the 32-bit count limit imposed by the
size of the ops count field) number or guidance in the NFS 4.0 spec on the
number of operations.  It does warn client implementors from making requests
unnecessarily complex, though.

I don't see any new guidance in the 4.1 spec, though that version introduces
the ability for systems to negotiate what the maximum op count can be.

I'd arbitrarily say that 128 is a very reasonable max.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.