You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Something I noticed after the release is that run_stats for intel_mp now means something slightly different than what it's intended to mean. In the docs, the run_stats option has this description:
Boolean indicating if this app instance should collect device statistics. One per physical NIC (conflicts with master_stats). There is a small but detectable run time performance hit incurred. The default is false.
In particular, each physical NIC should only have one app with the flag on. In the latest lwAFTR, we use the flag on multiple apps at once on a single NIC.
Instead, I think we should have NIC apps always sync their own RX/TX counters (regardless of what run_stats is) or maybe return to having one app always sync the stats (and find another way to show the queue counters in snabb top).
The text was updated successfully, but these errors were encountered:
Something I noticed after the release is that
run_stats
forintel_mp
now means something slightly different than what it's intended to mean. In the docs, therun_stats
option has this description:In particular, each physical NIC should only have one app with the flag on. In the latest lwAFTR, we use the flag on multiple apps at once on a single NIC.
Instead, I think we should have NIC apps always sync their own RX/TX counters (regardless of what
run_stats
is) or maybe return to having one app always sync the stats (and find another way to show the queue counters insnabb top
).The text was updated successfully, but these errors were encountered: