diff options
author | Jacob Keller <jacob.e.keller@intel.com> | 2017-02-07 01:38:45 +0300 |
---|---|---|
committer | Jeff Kirsher <jeffrey.t.kirsher@intel.com> | 2017-03-21 02:45:21 +0300 |
commit | 510dd4609f581329a421fa20e1b802b629bb7ee2 (patch) | |
tree | 631d5abfd66b8080f25ba24992071cda46629a62 /tools/perf/scripts/python/call-graph-from-sql.py | |
parent | 6d069425f0fcafff5bfdd292e5f345ce55d46a43 (diff) | |
download | linux-510dd4609f581329a421fa20e1b802b629bb7ee2.tar.xz |
i40e: don't re-enable ATR when flushing filters if SB has TCP4/IPv4 rules
When flushing and replaying FDIR filters, it is possible we would
disable ATR, and then re-enable it even though we should have kept
it disabled due to existing TCP/IPv4 filters. Fix this by checking
whether we have TCP4/IPv4 filters before re-enabling.
Alternatively, we could instead restore ATR and then replay filters,
however, this would cause us to rapidly enable and then disable ATR in
some cases.
Change-ID: I076e4cc1e4409bce7f98f3c213295433a4ff43d8
Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
Reviewed-by: Avinash Dayanand <avinash.dayanand@intel.com>
Reviewed-by: Alan Brady <alan.brady@intel.com>
Reviewed-by: Mitch Williams <mitch.a.williams@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-sql.py')
0 files changed, 0 insertions, 0 deletions