summaryrefslogtreecommitdiffstats
path: root/fs
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2024-08-23 02:00:30 +0200
committerJakub Kicinski <kuba@kernel.org>2024-08-23 02:00:31 +0200
commitbfc52deef5ed58d92cfbe68dbceee3102617a8df (patch)
tree314d0430cb85c23e099f477b63893ada01c9173f /fs
parentMerge branch 'enhance-network-interface-feature-testing' (diff)
parentipv4: Unmask upper DSCP bits when using hints (diff)
downloadlinux-bfc52deef5ed58d92cfbe68dbceee3102617a8df.tar.xz
linux-bfc52deef5ed58d92cfbe68dbceee3102617a8df.zip
Merge branch 'unmask-upper-dscp-bits-part-1'
Ido Schimmel says: ==================== Unmask upper DSCP bits - part 1 tl;dr - This patchset starts to unmask the upper DSCP bits in the IPv4 flow key in preparation for allowing IPv4 FIB rules to match on DSCP. No functional changes are expected. The TOS field in the IPv4 flow key ('flowi4_tos') is used during FIB lookup to match against the TOS selector in FIB rules and routes. It is currently impossible for user space to configure FIB rules that match on the DSCP value as the upper DSCP bits are either masked in the various call sites that initialize the IPv4 flow key or along the path to the FIB core. In preparation for adding a DSCP selector to IPv4 and IPv6 FIB rules, we need to make sure the entire DSCP value is present in the IPv4 flow key. This patchset starts to unmask the upper DSCP bits in the various places that invoke the core FIB lookup functions directly (patches #1-#7) and in the input route path (patches #8-#12). Future patchsets will do the same in the output route path. No functional changes are expected as commit 1fa3314c14c6 ("ipv4: Centralize TOS matching") moved the masking of the upper DSCP bits to the core where 'flowi4_tos' is matched against the TOS selector. ==================== Link: https://patch.msgid.link/20240821125251.1571445-1-idosch@nvidia.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions