On Mon, 15 Mar 2021 20:23:50 +0800 Huazhong Tan wrote: > From: Jian Shen <shenjia...@huawei.com> > > For device version V3, it supports queue bonding, which can > identify the tuple information of TCP stream, and create flow > director rules automatically, in order to keep the tx and rx > packets are in the same queue pair. The driver set FD_ADD > field of TX BD for TCP SYN packet, and set FD_DEL filed for > TCP FIN or RST packet. The hardware create or remove a fd rule > according to the TX BD, and it also support to age-out a rule > if not hit for a long time. > > The queue bonding mode is default to be disabled, and can be > enabled/disabled with ethtool priv-flags command.
This seems like fairly well defined behavior, IMHO we should have a full device feature for it, rather than a private flag. Does the device need to be able to parse the frame fully for this mechanism to work? Will it work even if the TCP segment is encapsulated in a custom tunnel?