diff options
| author | Eric Dumazet <[email protected]> | 2012-06-01 01:47:50 +0000 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2012-06-01 14:22:11 -0400 |
| commit | fff3269907897ee91406ece125795f53e722677e (patch) | |
| tree | 6c22d2afaea6bc6fd2b34311db9c80b5418b94d1 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 7433819a1eefd4e74711fffd6d54e30a644ef240 (diff) | |
tcp: reflect SYN queue_mapping into SYNACK packets
While testing how linux behaves on SYNFLOOD attack on multiqueue device
(ixgbe), I found that SYNACK messages were dropped at Qdisc level
because we send them all on a single queue.
Obvious choice is to reflect incoming SYN packet @queue_mapping to
SYNACK packet.
Under stress, my machine could only send 25.000 SYNACK per second (for
200.000 incoming SYN per second). NIC : ixgbe with 16 rx/tx queues.
After patch, not a single SYNACK is dropped.
Signed-off-by: Eric Dumazet <[email protected]>
Cc: Hans Schillstrom <[email protected]>
Cc: Jesper Dangaard Brouer <[email protected]>
Cc: Neal Cardwell <[email protected]>
Cc: Tom Herbert <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions