On Tue, Jan 14, 2025 at 6:30 AM Taehee Yoo <ap420073@xxxxxxxxx> wrote: > > The bnxt_en driver has configured the hds_threshold value automatically > when TPA is enabled based on the rx-copybreak default value. > Now the hds-thresh ethtool command is added, so it adds an > implementation of hds-thresh option. > > Configuration of the hds-thresh is applied only when > the tcp-data-split is enabled. The default value of > hds-thresh is 256, which is the default value of > rx-copybreak, which used to be the hds_thresh value. > > The maximum hds-thresh is 1023. > > # Example: > # 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 > > Tested-by: Stanislav Fomichev <sdf@xxxxxxxxxxx> > Tested-by: Andy Gospodarek <gospo@xxxxxxxxxxxx> > Signed-off-by: Taehee Yoo <ap420073@xxxxxxxxx> Thanks. Reviewed-by: Michael Chan <michael.chan@xxxxxxxxxxxx>
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
