Thread (14 messages) flat view 14 messages, 2 authors, 2020-11-16

Re: [PATCH V3 net-next 06/10] net: hns3: add ethtool priv-flag for DIM

From: Jakub Kicinski <kuba@kernel.org>
Date: 2020-11-16 18:12:55
Also in: lkml

On Mon, 16 Nov 2020 16:41:45 +0800 tanhuazhong wrote:
On 2020/11/15 2:54, Jakub Kicinski wrote:
quoted
On Thu, 12 Nov 2020 11:33:14 +0800 Huazhong Tan wrote:  
quoted
Add a control private flag in ethtool for enable/disable
DIM feature.

Signed-off-by: Huazhong Tan <redacted>  
Please work on a common ethtool API for the configuration instead of
using private flags.

Private flags were overused because the old IOCTL-based ethtool was
hard to extend, but we have a netlink API now.

For example here you're making a choice between device and DIM
implementation of IRQ coalescing. You can add a new netlink attribute
to the ETHTOOL_MSG_COALESCE_GET/ETHTOOL_MSG_COALESCE_SET commands which
controls the type of adaptive coalescing (if enabled).
The device's implementation of IRQ coalescing will be removed, if DIM 
works ok for a long time. So could this private flag for DIM be 
uptreamed as a transition scheme? And adding a new netlink attrtibute to 
controls the type of adaptive coalescing seems useless for other drivers.
The information whether the adaptive behavior is implemented by DIM,
device or custom driver implementation is useful regardless. Right now
users only see "adaptive" and don't know what implements it - device,
DIM or is it a custom implementation in the driver. So regardless if
you remove the priv flag, the "read"/"get" side of the information will
still be useful.

Besides you have another priv flag in this set that needs to be
converted to a generic attribute - the one for the timer reset
behavior.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help