summaryrefslogtreecommitdiff
path: root/net/core/devmem.c
diff options
context:
space:
mode:
authorTaehee Yoo <ap420073@gmail.com>2025-01-14 17:28:44 +0300
committerJakub Kicinski <kuba@kernel.org>2025-01-16 01:42:11 +0300
commiteec8359f0797ef87c6ef6cbed6de08b02073b833 (patch)
tree1f0778910d5a6538fb4ae860292c658ccab30dd3 /net/core/devmem.c
parent197258f0ef685ddbd534254dc79f49faa47dc93d (diff)
downloadlinux-eec8359f0797ef87c6ef6cbed6de08b02073b833.tar.xz
net: ethtool: add support for configuring hds-thresh
The hds-thresh option configures the threshold value of the header-data-split. If a received packet size is larger than this threshold value, a packet will be split into header and payload. The header indicates TCP and UDP header, but it depends on driver spec. The bnxt_en driver supports HDS(Header-Data-Split) configuration at FW level, affecting TCP and UDP too. So, If hds-thresh is set, it affects UDP and TCP packets. Example: # ethtool -G <interface name> hds-thresh <value> # ethtool -G enp14s0f0np0 tcp-data-split on hds-thresh 256 # ethtool -g enp14s0f0np0 Ring parameters for enp14s0f0np0: Pre-set maximums: ... HDS thresh: 1023 Current hardware settings: ... TCP data split: on HDS thresh: 256 The default/min/max values are not defined in the ethtool so the drivers should define themself. The 0 value means that all TCP/UDP packets' header and payload will be split. Tested-by: Stanislav Fomichev <sdf@fomichev.me> Signed-off-by: Taehee Yoo <ap420073@gmail.com> Link: https://patch.msgid.link/20250114142852.3364986-3-ap420073@gmail.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'net/core/devmem.c')
0 files changed, 0 insertions, 0 deletions