⬢ DragonFlyBSD Kernel Audit
DF-3194 / run.log
← back to finding ↓ download raw
# DF-3194 race campaign console excerpts (stock kernel, guest stayed UP throughout)
#
# run 1 (fill=16000, 12 threads, host CPU hogs):
[fill] done in 7.10s - nfsnode hash bucket is deep now
[fill] 200 cached re-stats in 244.624 ms
[hammer] 12 threads x 40000 rounds of same-name stat races
[hammer] round 500/40000 (79.2 rps)
...
[hammer] round 15500/40000 (67.2 rps)   # killed early for reconfiguration
#
# run 2 (fill=58000, +2x loopback UDP flood):
[fill] done in 7.10s  ->  [fill] done in ...s
[hammer] 12 threads x 18000 rounds ...
[hammer] round 17500/18000 (45.9 rps)
[hammer] finished 18000 rounds without a panic
TRIGGER_RC=0 (reaching this line means no panic)
#
# run 3 (fill=76000 idx range, +6x memhog, 10 host hogs, +2x udp_flood):
[fill] done in 414.84s - nfsnode hash bucket is deep now
[fill] 200 cached re-stats in 2211.715 ms
[hammer] 12 threads x 24000 rounds of same-name stat races
[hammer] round 10000/24000 (31.8 rps)
...
[hammer] round 23500/24000 (30.1 rps)
[hammer] finished 24000 rounds without a panic
TRIGGER_RC=$? (reaching this line means no panic)
#
# totals: ~620k barrier-synchronised 12-thread same-fh nfs_nget races, no panic.
# guest remained up after every run (vm.sh status: up).