This action object resets all the accumulated SCSI statistics counters for this specific flow when set to clear(1), while setting or reading it as noop(2) does nothing, and per the desc a read always returns noop(2) regardless of what was last written. An admin who just changed a flow's configuration (say, adjusted write-acceleration settings) sets this to clear(1) to zero out the old counters and get a clean baseline for evaluating the new configuration's effect. Because reads never reflect a 'just cleared' state, the admin cannot use this object to confirm a clear actually happened - they would instead check that the read/write counters themselves dropped to zero afterward.