Project

General

Profile

Actions

Optimization #3637

closed

Performance impact of Cisco Fabricpath

Added by Andreas Herz about 4 years ago. Updated 10 months ago.

Status:
Closed
Priority:
Normal
Target version:
Effort:
Difficulty:
Label:

Description

At some setups we see Cisco Fabricpath Traffic (ethertype 0x8903) that results in rather high drop rates even though the traffic is not responsible for much load. With a bpf filter to that protocol the issue was gone.


Files

813_a.txt (7.68 KB) 813_a.txt Andreas Herz, 04/14/2020 03:35 PM
813_b.txt (7.66 KB) 813_b.txt Andreas Herz, 04/14/2020 03:35 PM
d11_a.txt (7.6 KB) d11_a.txt Andreas Herz, 04/14/2020 03:35 PM
d11_b.txt (7.35 KB) d11_b.txt Andreas Herz, 04/14/2020 03:35 PM
perftop.png (28.5 KB) perftop.png Andreas Herz, 04/14/2020 03:35 PM

Subtasks 1 (0 open1 closed)

Optimization #6229: Performance impact of Cisco Fabricpath (6.0.x backport)ClosedPhilippe AntoineActions

Related issues 1 (0 open1 closed)

Related to Suricata - Bug #6394: Sudden increase in capture.kernel_drops and tcp.pkt_on_wrong_thread after upgrading to 6.0.14ClosedPhilippe AntoineActions
Actions #1

Updated by Victor Julien about 4 years ago

Do you have more info about what you're seeing? Any decoder events, perf stats, etc?

Updated by Andreas Herz about 4 years ago

Two systems with no filter active (case a) and bpf filter active (case b). Also a perf top from those machines running without the bpf filter. The left one is another machine with low traffic and not that much traffic at all but quite some amount of it being cisco fabric path.

Actions #3

Updated by Peter Manev about 4 years ago

Out of curiosity - any chance of knowing whats the "unknown" function on top of the leftmost pertop?

Actions #4

Updated by Andreas Herz about 4 years ago

Peter Manev wrote in #note-3:

Out of curiosity - any chance of knowing whats the "unknown" function on top of the leftmost pertop?

I didn't had a change to find it yet, when I zoom in I see nothing. I agree that this is rather strange.

Actions #5

Updated by Peter Manev about 4 years ago

Btw - there are some functions/calls that can be unknown , just havn't seen an "unknown" with so high usage - was my point.

Actions #6

Updated by Philippe Antoine 11 months ago

  • Status changed from New to In Review
  • Assignee set to Philippe Antoine
  • Target version changed from TBD to 8.0.0-beta1
Actions #7

Updated by Philippe Antoine 10 months ago

  • Target version changed from 8.0.0-beta1 to 7.0.1
Actions #8

Updated by Philippe Antoine 10 months ago

  • Priority changed from Low to Normal
Actions #9

Updated by Philippe Antoine 10 months ago

  • Label Needs backport, Needs backport to 6.0 added
Actions #10

Updated by Victor Julien 10 months ago

  • Status changed from In Review to Resolved
Actions #11

Updated by OISF Ticketbot 10 months ago

  • Subtask #6229 added
Actions #12

Updated by OISF Ticketbot 10 months ago

  • Label deleted (Needs backport, Needs backport to 6.0)
Actions #13

Updated by Victor Julien 10 months ago

  • Status changed from Resolved to Closed
Actions #14

Updated by Victor Julien 7 months ago

  • Related to Bug #6394: Sudden increase in capture.kernel_drops and tcp.pkt_on_wrong_thread after upgrading to 6.0.14 added
Actions

Also available in: Atom PDF