[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	8810
Summary	nfs4: allow filtering on opnames like "nfs.main_opcode==WRITE"
Classification	Unclassified
Product	Wireshark
Version	SVN
Hardware	x86
OS	All
Status	UNCONFIRMED
Severity	Minor
Priority	Low
Component	Dissection engine (libwireshark)
Assignee	bugzilla-admin@wireshark.org
Reporter	ndevos@redhat.com
Attachment #10999 Flags	review_for_checkin?

Created attachment 10999 [details]
Use value_string array names_nfs4_operation_ext for nfs.main_opname, just like
nfs.opname does

Build Information:

--
One can now use filters like this, without needing to know the number of
the operation.

Example:

  $ ./tshark -r dump.pcap.gz -q \
    -z rpc,srt,100003,4,nfs.main_opcode==WRITE

  ==================================================================
  NFS Version 4 SRT Statistics:
  Filter: nfs.main_opcode==WRITE
  Procedure        Calls    Min SRT    Max SRT    Avg SRT    Total
  COMPOUND          4875   0.000191   0.038207   0.002282  11.126054
  ==================================================================


Currently one needs to know that WRITE has value 38, and use this number
in the filter. This change makes filtering more user friendly, just like
filtering on nfs.opcode already allows.

---

      You are receiving this mail because:

• You are watching all bug changes.