diff options
| author |   Neale Ranns <nranns@cisco.com> | 2019-04-02 08:13:33 +0000 |
|---|---|---|
| committer |   Damjan Marion <dmarion@me.com> | 2019-12-17 17:57:24 +0000 |
| commit | f62a8c013c6e22c012b9d7df2ef463a6370cf1ce (patch) | |
| tree | 0448d4b53340b84e1a8aca87ec57133c503026da /src/vlibmemory | |
| parent | f2bde7ac51123a0a46334b4ec55e2aceae031db7 (diff) | |
ipsec: bind an SA to a worker
the sequence number increment and the anti-replay window
checks must be atomic. Given the vector nature of VPP we
can't simply use atomic increments for sequence numbers,
since a vector on thread 1 with lower sequence numbers could
be 'overtaken' by packets on thread 2 with higher sequence
numbers.
The anti-replay logic requires a critical section, not just
atomics, and we don't want that.
So when the SA see the first packet it is bound to that worker
all subsequent packets, that arrive on a different worker,
are subject to a handoff.
Type: feature
Change-Id: Ia20a8645fb50622ea6235ab015a537f033d531a4
Signed-off-by: Neale Ranns <nranns@cisco.com>
Diffstat (limited to 'src/vlibmemory')
0 files changed, 0 insertions, 0 deletions