summaryrefslogtreecommitdiff
path: root/security
diff options
context:
space:
mode:
authorPaolo Abeni <pabeni@redhat.com>2024-02-22 15:31:25 +0100
committerPaolo Abeni <pabeni@redhat.com>2024-02-22 15:31:25 +0100
commit85badb2c008a460f8b4cf064e1dce7c0752bec1c (patch)
treee3845e73917787ffc4f1bb6cb3b744d93d9bf101 /security
parente7b83f2fa445290f4ce906367ccfc8d184a98249 (diff)
parentf6eff053a60c4c501baae29f245e66a67494dffb (diff)
Merge branch 'bnxt_en-ntuple-filter-improvements'
Michael Chan says: ==================== bnxt_en: Ntuple filter improvements The current Ntuple filter implementation has a limitation on 5750X (P5) and newer chips. The destination ring of the ntuple filter must be a valid ring in the RSS indirection table. Ntuple filters may not work if the RSS indirection table is modified by the user to only contain a subset of the rings. If an ntuple filter is set to a ring destination that is not in the RSS indirection table, the packet matching that filter will be placed in a random ring instead of the specified destination ring. This series of patches will fix the problem by using a separate VNIC for ntuple filters. The default VNIC will be dedicated for RSS and so the indirection table can be setup in any way and will not affect ntuple filters using the separate VNIC. Quite a bit of refactoring is needed to do the the VNIC and RSS context accounting in the first few patches. This is technically a bug fix, but I think the changes are too big for -net. ==================== Link: https://lore.kernel.org/r/20240220230317.96341-1-michael.chan@broadcom.com Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions