Skip to content

Limit the number of LFT->UFT references allowed - #1039

Draft
FelixMcFelix wants to merge 6 commits into
masterfrom
bound-my-list
Draft

Limit the number of LFT->UFT references allowed#1039
FelixMcFelix wants to merge 6 commits into
masterfrom
bound-my-list

Conversation

@FelixMcFelix

Copy link
Copy Markdown
Collaborator

XXX Expand

  • UFT table entries have the wrong expiry policy, and TCP flows can
    thrash heavily rather than blocking insertion.
  • Eviction should not delegate cleanup of child references to the
    periodic task.
  • The number of child references on any FlowEntry should be limited to
    prevent unbounded growth -- we expect this to be 2 active children per
    hit LFT!

XXX Expand

* UFT table entries have the wrong expiry policy, and TCP flows can
  thrash heavily rather than blocking insertion.
* Eviction should not delegate cleanup of child references to the
  periodic task.
* The number of child references on any FlowEntry should be limited to
  prevent unbounded growth -- we expect this to be 2 active children per
  hit LFT!
We're evidently getting something wrong when searching for candidates.
Empty lists are liable to stay empty, this appears to save some percent
on table sizes up to what we're using in xde.
Trying to get some baselines to understand what it's going to cost to
move some of theeviction score calculation into the periodic. The bad
news is that said periodic can already be wickedly expensive.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant